Is Auteur safe to use?

Auteur has an HVTrust score of 42.7/100 (Grade D), ranked #304 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Auteur?

Auteur scores 42.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.0k GitHub stars and is categorized under Agent Skills.

Auteur

agiwhitelist/auteur

The Claude Code skill that directs a website like a film. Commit-sheet, generated assets, build, and an executable anti-slop linter that gates every ship.

Agent Skills JavaScript Listed MIT

Is Auteur safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 0%

Last push 51d ago

Compare Auteur

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Auteur scores 42.7/100 (Grade D), ranked #304 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.1/10; recent commits are unsigned; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Auteur compares in Agent Skills

Bars show each HVTrust score; the tick marks Auteur’s 42.7.

Where the 42.7 comes from

HVTrust dimensions vs the Agent Skills average

42.7 / 100 · 100.0% confidence

Auteur Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

3.9 / 25

4.2 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.6 / 20

5.6 below avg 14.2

AdoptionLog-scaled stars · package downloads

8.6 / 20

in line with avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 17 spots (#285 → #302)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Rank Moved

Rank rose 44 spots (#328 → #284)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 51 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Auteur View Agent Skills Report missing data

42.0

Activity sub-score · out of 100

#304

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

1.0k

Forks

Last Push

2026-08-06

51 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #302

Analysis

Activity Inputs

42.0 / 100

StarsRepository reach

18.1 / 30

FreshnessLast push recency

17.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Auteur

Public trust evidence for Auteur is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Auteur publish package provenance?

No published build provenance is currently detected for Auteur. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Auteur have an OpenSSF Scorecard?

Auteur has an OpenSSF Scorecard score of 3.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Auteur actively maintained?

Slowing down. Last push was 51 days ago — keep an eye on whether activity resumes.

What license does Auteur use?

Auteur ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Auteur's commits signed?

0% of the last 100 commits to Auteur are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Auteur's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

Maintain Auteur?

For maintainers

HVTrust scores Auteur from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 17 spots (#285 → #302)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Rank Moved

Rank rose 44 spots (#328 → #284)

2026-09-23

HVTrust Changed

HVTrust up 20.0pts (22.3 → 42.3)

2026-09-22

Newly Listed

First tracked at rank #328

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 11 spots (#253 → #264)

2026-09-10

Rank Moved

Rank dropped 11 spots (#242 → #253)

2026-09-05

Rank Moved

Rank dropped 17 spots (#201 → #218)

2026-09-04

Rank Moved

Rank dropped 20 spots (#181 → #201)

2026-09-04

Activity Score Changed

Activity score down 9pts (57 → 48)

2026-09-03

Rank Moved

Rank dropped 13 spots (#168 → #181)

2026-09-02

Rank Moved

Rank dropped 12 spots (#156 → #168)

2026-09-01

Rank Moved

Rank dropped 11 spots (#145 → #156)

2026-08-31

Scorecard Added

OSSF Scorecard: 3.1/10

2026-08-31

Rank Moved

Rank rose 77 spots (#222 → #145)

2026-08-31

HVTrust Changed

HVTrust up 20.6pts (28.2 → 48.8)

2026-08-30

Rank Moved

Rank dropped 38 spots (#184 → #222)

2026-08-29

Rank Moved

Rank dropped 39 spots (#145 → #184)

2026-08-28

Rank Moved

Rank dropped 26 spots (#119 → #145)

2026-08-27

Rank Moved

Rank dropped 21 spots (#98 → #119)

2026-08-26

Rank Moved

Rank dropped 63 spots (#35 → #98)

2026-08-11

Newly Listed

First tracked at rank #30

GitHub → npm: auteur

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/auteur.svg)](https://hvtracker.net/agents/auteur)
            
HTML:
            <a href="https://hvtracker.net/agents/auteur"><img src="https://hvtracker.net/badge/auteur.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON