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. Full methodology →
Signals refreshed2026-06-24 18:00 UTC·Repo last pushed today
Activity & Reach
Stars
44.7k
Forks
7.9k
Last Push
2026-06-24
today
Commits (4 wk)
494
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
273
Rank Change
NEW
Analysis
HVTrust Dimensions
62.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.3 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
11.2 / 20
Activity Inputs
96.0 / 100
StarsRepository reach
27.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.7 / 10
OpenSSF Scorecard · scanned Jun 24, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests8
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy4
Signed-Releases-1
Token-Permissions10
Vulnerabilities0
Is Nanobot safe?
Nanobot 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 Nanobot publish package provenance?
No published build provenance is currently detected for Nanobot. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Nanobot have an OpenSSF Scorecard?
Nanobot has an OpenSSF Scorecard score of 5.7/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 Nanobot actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Nanobot use?
Nanobot ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Nanobot's commits signed?
0% of the last 100 commits to Nanobot 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Amazon Bedrock
Anthropic
Azure OpenAI
Firecrawl
Google Gemini
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
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 Nanobot?
HVTrust scores Nanobot 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.
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 v3.2 · Raw JSON
