PentestAgent

PentestAgent is an AI agent framework for black-box security testing, supporting bug bounty, red-team, and penetration t

Security & Guardrails Python Grade C Listed MIT
56.7/100
Rank #261 of 468
Compare PentestAgent

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-04 · 2d ago
Recent change
No recent signal change

Is PentestAgent safe? PentestAgent scores 56.7/100 (Grade C), ranked #261 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.1/10; 41% of recent commits are signed; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-26
Rank Moved
Rank rose 14 spots (#269 → #255)
2026-07-15
Rank Moved
Rank dropped 11 spots (#246 → #257)
2026-07-14
Rank Moved
Rank dropped 16 spots (#230 → #246)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.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.
70.4
Activity sub-score · out of 100
#8

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

Signals refreshed 2026-08-06 02:30 UTC · Repo last pushed 2 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
2.9k
Forks
576
Last Push
2026-08-04
2 days ago
Commits (4 wk)
8
Downloads (7d)
HN mentions (30d)
Open Issues
14
Rank Change
▼2
was #259

Analysis

HVTrust Dimensions vs Security & Guardrails

56.7 / 100 · 100.0% confidence

PentestAgent Security & Guardrails average (14 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.7 / 25
0.7 above avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.3 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
15.7 / 20
0.9 below avg 16.6
AdoptionLog-scaled stars · package downloads
8.3 / 20
2.4 below avg 10.7

Activity Inputs

70.4 / 100
StarsRepository reach
20.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
12.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.1 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
41%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 7
CII-Best-Practices 0
Code-Review 4
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 10

Is PentestAgent safe?

PentestAgent has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does PentestAgent publish package provenance?
No published build provenance is currently detected for PentestAgent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does PentestAgent have an OpenSSF Scorecard?
PentestAgent has an OpenSSF Scorecard score of 6.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 PentestAgent actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does PentestAgent use?
PentestAgent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are PentestAgent's commits signed?
41% of the last 100 commits to PentestAgent 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.

Compare PentestAgent head-to-head

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
high confidence
Implemented
PentestAgent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • code
  • search
  • shell
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 PentestAgent?

For maintainers

HVTrust scores PentestAgent 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.

Reputation Timeline

Signal history
Rank 7Score 2Listed 1HVTrust 1Grade 1Scorecard 1
2026-07-26
Rank Moved
Rank rose 14 spots (#269 → #255)
2026-07-15
Rank Moved
Rank dropped 11 spots (#246 → #257)
2026-07-14
Rank Moved
Rank dropped 16 spots (#230 → #246)
2026-07-13
Rank Moved
Rank dropped 28 spots (#202 → #230)
2026-07-07
Activity Score Changed
Activity score up 6pts (62 → 68)
2026-06-26
Rank Moved
Rank dropped 16 spots (#190 → #206)
2026-06-26
Activity Score Changed
Activity score down 7pts (71 → 64)
2026-06-24
Scorecard Added
OSSF Scorecard: 6.1/10
2026-06-24
Grade Changed
Trust grade D → C
2026-06-24
Rank Moved
Rank rose 101 spots (#289 → #188)
2026-06-24
HVTrust Changed
HVTrust up 35.5pts (22.9 → 58.4)
2026-06-21
Rank Moved
Rank dropped 23 spots (#255 → #278)
2026-06-20
Newly Listed
First tracked at rank #255

Embed Badge Badge guide for maintainers →

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

Other agents in Security & Guardrails

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