Is Nanobot safe to use?

Nanobot has an HVTrust score of 59.7/100 (Grade C), ranked #642 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Nanobot?

Nanobot scores 59.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 48.6k GitHub stars and is categorized under Agent Frameworks.

Nanobot

HKUDS/nanobot

Ultra-lightweight, open-source, self-hosted personal AI agent framework in Python with WebUI, tools, memory, MCP, multi-agent workflows, automation, and chat apps

Agent Frameworks Python Listed MIT

Is Nanobot safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance None

Signed commits 9%

Last push today

Compare Nanobot

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Nanobot scores 59.7/100 (Grade C), ranked #642 of 1325 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 4.3/10; 9% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Nanobot compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Nanobot’s 59.7.

Where the 59.7 comes from

HVTrust dimensions vs the Agent Frameworks average

59.7 / 100 · 100.0% confidence

Nanobot Agent Frameworks average (122 agents)

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

5.8 / 25

4.0 below avg 9.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.5

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

6.2 above avg 13.8

AdoptionLog-scaled stars · package downloads

11.2 / 20

in line with avg 11.2

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 24 spots (#615 → #639)

2026-09-23

Rank Moved

Rank dropped 372 spots (#238 → #610)

2026-09-21

Rank Moved

Rank rose 371 spots (#608 → #237)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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.

Compare with another agent Get email alerts for Nanobot View Agent Frameworks Report missing data

96.4

Activity sub-score · out of 100

#56

In Agent Frameworks

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

48.6k

Forks

8.6k

Last Push

2026-09-26

today

Commits (4 wk)

393

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

216

Rank Change

▼3

was #639

Analysis

Activity Inputs

96.4 / 100

StarsRepository reach

28.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

18.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 4

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Nanobot

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 4.3/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?

9% 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

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

medium confidence

Implemented

Nanobot 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.

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

How this surface has changed

Detected changes to Nanobot'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-02

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Nanobot?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 24 spots (#615 → #639)

2026-09-23

Rank Moved

Rank dropped 372 spots (#238 → #610)

2026-09-21

Rank Moved

Rank rose 371 spots (#608 → #237)

2026-09-13

Rank Moved

Rank dropped 15 spots (#581 → #596)

2026-09-11

Rank Moved

Rank dropped 19 spots (#564 → #583)

2026-09-07

Rank Moved

Rank dropped 39 spots (#514 → #553)

2026-09-05

Rank Moved

Rank dropped 69 spots (#443 → #512)

2026-09-04

Rank Moved

Rank dropped 23 spots (#420 → #443)

2026-09-03

Rank Moved

Rank dropped 19 spots (#401 → #420)

2026-09-02

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Rank Moved

Rank rose 82 spots (#483 → #401)

2026-09-02

HVTrust Changed

HVTrust up 3.9pts (57.1 → 61.0)

2026-09-01

Rank Moved

Rank dropped 10 spots (#473 → #483)

2026-08-31

Rank Moved

Rank dropped 29 spots (#444 → #473)

2026-08-29

Rank Moved

Rank dropped 15 spots (#438 → #453)

2026-08-27

Rank Moved

Rank dropped 11 spots (#424 → #435)

2026-08-26

Rank Moved

Rank dropped 42 spots (#382 → #424)

2026-08-24

Rank Moved

Rank dropped 22 spots (#360 → #382)

2026-08-22

Rank Moved

Rank rose 19 spots (#381 → #362)

2026-08-18

Rank Moved

Rank dropped 45 spots (#327 → #372)

2026-08-17

Rank Moved

Rank rose 15 spots (#342 → #327)

2026-08-13

Rank Moved

Rank dropped 16 spots (#322 → #338)

2026-08-12

Rank Moved

Rank rose 22 spots (#344 → #322)

2026-08-10

Rank Moved

Rank dropped 22 spots (#328 → #350)

2026-08-08

Rank Moved

Rank dropped 79 spots (#248 → #327)

2026-07-30

Rank Moved

Rank rose 11 spots (#258 → #247)

2026-07-28

Rank Moved

Rank dropped 19 spots (#233 → #252)

2026-07-23

Rank Moved

Rank dropped 10 spots (#231 → #241)

2026-07-14

Rank Moved

Rank dropped 12 spots (#209 → #221)

2026-07-13

Rank Moved

Rank dropped 34 spots (#175 → #209)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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