Is AutoCVE safe to use?

AutoCVE has an HVTrust score of 18.7/100 (Grade D), ranked #1142 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for AutoCVE?

AutoCVE scores 18.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.3k GitHub stars and is categorized under Security & Guardrails.

AutoCVE

larlarua/AutoCVE

Agent-driven automated CVE discovery platform for source code auditing, vulnerability verification, and report generatio

Security & Guardrails Python Grade D Listed AGPL-3.0

18.7/100

Rank #1142 of 1308

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-07 · 12d ago

Recent change

Rank

Is AutoCVE safe? AutoCVE scores 18.7/100 (Grade D), ranked #1142 of 1308 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; 20% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#16 CyberStrike — 24.4 (D) → #17 T3MP3ST — 23.9 (D) → #18 pentest-ai — 21.5 (D) → #20 auto-re-agent — 18.1 (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-16

Rank Moved

Rank dropped 29 spots (#1116 → #1145)

2026-08-10

Rank Moved

Rank dropped 73 spots (#1022 → #1095)

2026-08-08

Rank Moved

Rank dropped 526 spots (#489 → #1015)

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

60.9

Activity sub-score · out of 100

#19

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

1.3k

Forks

Last Push

2026-08-07

12 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #1135

Analysis

HVTrust Dimensions vs Security & Guardrails

18.7 / 100 · 50.0% confidence

AutoCVE Security & Guardrails average (20 agents)

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

1.0 / 25

8.0 below avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.4 below avg 11.9

Maintenance60% last-push freshness · 40% commit activity

14.3 / 20

2.3 below avg 16.6

AdoptionLog-scaled stars · package downloads

7.4 / 20

2.8 below avg 10.2

Activity Inputs

60.9 / 100

StarsRepository reach

18.6 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

9.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

20%

of last 100 commits verified

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?

Maintained. Last push was 12 days ago.

What license does AutoCVE use?

AutoCVE ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are AutoCVE's commits signed?

20% of the last 100 commits to AutoCVE 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

high confidence

5 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

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

2026-08-16

Rank Moved

Rank dropped 29 spots (#1116 → #1145)

2026-08-10

Rank Moved

Rank dropped 73 spots (#1022 → #1095)

2026-08-08

Rank Moved

Rank dropped 526 spots (#489 → #1015)

2026-08-06

Newly Listed

First tracked at rank #494

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON