Is neuro-san-studio safe to use?

neuro-san-studio has an HVTrust score of 64.0/100 (Grade C), ranked #490 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for neuro-san-studio?

neuro-san-studio scores 64.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k GitHub stars and is categorized under Agent Frameworks.

neuro-san-studio

cognizant-ai-lab/neuro-san-studio

A playground for neuro-san

Agent Frameworks Python Grade C Listed Apache-2.0

64.0/100

Rank #490 of 1328

Compare neuro-san-studio

How does it stack up against its Agent Frameworks 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-09-20 · 0d ago

Recent change

Rank

Is neuro-san-studio safe? neuro-san-studio scores 64.0/100 (Grade C), ranked #490 of 1328 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 8.2/10; 49% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#38 Semantic Kernel — 65.9 (B) → #39 Eliza — 65.4 (B) → #41 QwenPaw — 64.0 (C) → #42 aeon — 63.2 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-17

Rank Moved

Rank dropped 18 spots (#478 → #496)

2026-09-11

Rank Moved

Rank dropped 13 spots (#462 → #475)

2026-09-07

Rank Moved

Rank dropped 24 spots (#418 → #442)

Maintainer Checklist

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 neuro-san-studio View Agent Frameworks Report missing data

79.7

Activity sub-score · out of 100

#40

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-20

Activity & Reach

Stars

1.1k

Forks

296

Last Push

2026-09-20

today

Commits (4 wk)

183

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

114

Rank Change

was #490

Analysis

HVTrust Dimensions vs Agent Frameworks

64.0 / 100 · 100.0% confidence

neuro-san-studio Agent Frameworks average (122 agents)

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

12.7 / 25

3.0 above avg 9.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

15.5 / 17

3.1 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

6.1 above avg 13.9

AdoptionLog-scaled stars · package downloads

7.3 / 20

3.9 below avg 11.2

Activity Inputs

79.7 / 100

StarsRepository reach

18.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

8.2 / 10

OpenSSF Scorecard · scanned Sep 17, 2026

Signed Commits

49%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 5

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 8

Is neuro-san-studio safe?

neuro-san-studio 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 neuro-san-studio publish package provenance?

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

Does neuro-san-studio have an OpenSSF Scorecard?

neuro-san-studio has an OpenSSF Scorecard score of 8.2/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 neuro-san-studio actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does neuro-san-studio use?

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

Are neuro-san-studio's commits signed?

49% of the last 100 commits to neuro-san-studio 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

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

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

Maintain neuro-san-studio?

For maintainers

HVTrust scores neuro-san-studio 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-17

Rank Moved

Rank dropped 18 spots (#478 → #496)

2026-09-11

Rank Moved

Rank dropped 13 spots (#462 → #475)

2026-09-07

Rank Moved

Rank dropped 24 spots (#418 → #442)

2026-09-06

Rank Moved

Rank dropped 10 spots (#408 → #418)

2026-09-05

Scorecard Added

OSSF Scorecard: 8.5/10

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 876 spots (#1284 → #408)

2026-09-05

HVTrust Changed

HVTrust up 42.2pts (22.2 → 64.4)

2026-09-04

Rank Moved

Rank dropped 10 spots (#1274 → #1284)

2026-09-03

Rank Moved

Rank dropped 23 spots (#1251 → #1274)

2026-09-02

Rank Moved

Rank dropped 27 spots (#1224 → #1251)

2026-09-01

Rank Moved

Rank dropped 25 spots (#1199 → #1224)

2026-08-31

Rank Moved

Rank dropped 26 spots (#1173 → #1199)

2026-08-30

Rank Moved

Rank dropped 33 spots (#1140 → #1173)

2026-08-29

Rank Moved

Rank dropped 30 spots (#1110 → #1140)

2026-08-28

Rank Moved

Rank dropped 24 spots (#1086 → #1110)

2026-08-27

Rank Moved

Rank dropped 17 spots (#1069 → #1086)

2026-08-26

Rank Moved

Rank dropped 73 spots (#996 → #1069)

2026-08-24

Rank Moved

Rank dropped 14 spots (#982 → #996)

2026-08-22

Rank Moved

Rank rose 10 spots (#994 → #984)

2026-08-17

Rank Moved

Rank rose 19 spots (#1012 → #993)

2026-08-16

Rank Moved

Rank dropped 37 spots (#975 → #1012)

2026-08-12

Rank Moved

Rank rose 11 spots (#981 → #970)

2026-08-10

Rank Moved

Rank dropped 49 spots (#926 → #975)

2026-08-08

Rank Moved

Rank dropped 433 spots (#478 → #911)

2026-08-06

Newly Listed

First tracked at rank #471

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/neuro-san-studio.svg)](https://hvtracker.net/agents/neuro-san-studio)
            
HTML:
            <a href="https://hvtracker.net/agents/neuro-san-studio"><img src="https://hvtracker.net/badge/neuro-san-studio.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