Is Nanobrowser safe to use?

Nanobrowser has an HVTrust score of 34.3/100 (Grade D), ranked #402 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Nanobrowser?

Nanobrowser scores 34.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 13.5k GitHub stars and is categorized under Browser & Computer Use.

Nanobrowser

nanobrowser/nanobrowser

Open-Source Chrome extension for AI-powered web automation. Run multi-agent workflows using your own LLM API key. Altern

Browser & Computer Use TypeScript Grade D Listed Apache-2.0

34.3/100

Rank #402 of 468

Compare Nanobrowser

How does it stack up against its Browser & Computer Use 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 C · 2/5 signals

Last push

2025-11-24 · 255d ago

Recent change

No recent signal change

Is Nanobrowser safe? Nanobrowser scores 34.3/100 (Grade D), ranked #402 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 2.8/10; 27% of recent commits are signed; last pushed 2025-11-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#24 Agent-E — 36.7 (D) → #25 OpenBrowser — 34.9 (D) → #27 ScaleCUA — 29.6 (D) → #28 PyWinAssistant — 29.2 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-29

Rank Moved

Rank dropped 11 spots (#393 → #404)

2026-07-15

Rank Moved

Rank dropped 25 spots (#365 → #390)

2026-07-14

Rank Moved

Rank dropped 20 spots (#345 → #365)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 255 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Nanobrowser View Browser & Computer Use Report missing data

39.5

Activity sub-score · out of 100

#26

In Browser & Computer Use

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 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-07-05 2026-08-06

Activity & Reach

Stars

13.5k

Forks

1.4k

Last Push

2025-11-24

255 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #402

Analysis

HVTrust Dimensions vs Browser & Computer Use

34.3 / 100 · 100.0% confidence

Nanobrowser Browser & Computer Use average (31 agents)

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

4.9 / 25

3.3 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

10.9 / 17

in line with avg 11.3

Maintenance60% last-push freshness · 40% commit activity

0 / 20

11.3 below avg 11.3

AdoptionLog-scaled stars · package downloads

9.9 / 20

1.2 below avg 11.1

Activity Inputs

39.5 / 100

StarsRepository reach

24.8 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

14.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.8 / 10

OpenSSF Scorecard · scanned Aug 5, 2026

Signed Commits

27%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 0

CII-Best-Practices 0

Code-Review 2

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 9

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0

Is Nanobrowser safe?

Public trust evidence for Nanobrowser 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 Nanobrowser publish package provenance?

No published build provenance is currently detected for Nanobrowser. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Nanobrowser have an OpenSSF Scorecard?

Nanobrowser has an OpenSSF Scorecard score of 2.8/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 Nanobrowser actively maintained?

Stale. The repository has not been pushed to in 255 days. Consider whether the project is still being maintained.

What license does Nanobrowser use?

Nanobrowser ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Nanobrowser's commits signed?

27% of the last 100 commits to Nanobrowser 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

3 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

browser
code

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 Nanobrowser?

For maintainers

HVTrust scores Nanobrowser 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-07-29

Rank Moved

Rank dropped 11 spots (#393 → #404)

2026-07-15

Rank Moved

Rank dropped 25 spots (#365 → #390)

2026-07-14

Rank Moved

Rank dropped 20 spots (#345 → #365)

2026-07-13

Rank Moved

Rank dropped 36 spots (#309 → #345)

2026-06-24

Rank Moved

Rank dropped 35 spots (#265 → #300)

2026-06-23

Scorecard Added

OSSF Scorecard: 2.8/10

2026-06-23

Rank Moved

Rank rose 35 spots (#300 → #265)

2026-06-23

HVTrust Changed

HVTrust up 21.2pts (15.3 → 36.5)

2026-06-21

Newly Listed

First tracked at rank #299

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Browser & Computer Use

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