updated 2026-08-06 16:30 UTC

AutoCVE

larlarua/AutoCVE

Pending first signal refresh

Security & Guardrails Python Grade D Listed
17.4/100
Rank #494 of 522
Compare AutoCVE

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-05 · 1d ago
Recent change
New

Is AutoCVE safe? AutoCVE scores 17.4/100 (Grade D), ranked #494 of 522 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#13 T3MP3ST — 24.9 (D) → #14 CyberStrike — 24.6 (D) → #16 auto-re-agent — 16.9 (D) → #17 pentest-ai — 16.8 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-06
Newly Listed
First tracked at rank #494
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Compare with another agent Get email alerts for AutoCVE View Security & Guardrails Report missing data
67.3
Activity sub-score · out of 100
#15
In Security & Guardrails

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-06 16:30 UTC · Repo last pushed yesterday

Activity & Reach

Stars
1.2k
Forks
90
Last Push
2026-08-05
yesterday
Commits (4 wk)
14
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
12
Rank Change
NEW

Analysis

HVTrust Dimensions vs Security & Guardrails

17.4 / 100 · 50.0% confidence

AutoCVE Security & Guardrails average (17 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
7.4 below avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
10.2 below avg 10.2
Maintenance60% last-push freshness · 40% commit activity
16.6 / 20
in line with avg 16.5
AdoptionLog-scaled stars · package downloads
7.4 / 20
2.8 below avg 10.2

Activity Inputs

67.3 / 100
StarsRepository reach
18.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
14.7 / 25
CommunityFork signal
9.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
—
Unable to query

Is AutoCVE safe?

Public trust evidence for AutoCVE 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 AutoCVE publish package provenance?
No published build provenance is currently detected for AutoCVE. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AutoCVE have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for AutoCVE. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is AutoCVE actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does AutoCVE use?
AutoCVE ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain AutoCVE?

For maintainers

HVTrust scores AutoCVE 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
Listed 1
2026-08-06
Newly Listed
First tracked at rank #494
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 17.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/autocve.svg)](https://hvtracker.net/agents/autocve)
HTML:
<a href="https://hvtracker.net/agents/autocve"><img src="https://hvtracker.net/badge/autocve.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON