updated 2026-11-10 04:07 UTC

NitroStack

Repository Website

The full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.

Protocols & Tool Integration TypeScript Listed Apache-2.0

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

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 89%
Last push yesterday
Advisories None known
Compare NitroStack

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: NitroStack scores 71.2/100 (Grade B), ranked #345 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 89% of recent commits are signed; no published advisory affects its latest release (@nitrostack/core); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How NitroStack could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships NitroStack and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/nitrocloudofficial/nitrostack, Apache-2.0, last pushed 2026-11-09. 89% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Oct 19, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 0
    Branch-Protection 5
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 9
    Contributors 3
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm @nitrostack/core Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @nitrostack/core 1.1.3. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues NitroStack’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How NitroStack compares in Protocols & Tool Integration

  1. #15 Treg 71.7 +0.5
  2. #16 ToolHive 71.2 ±0
  3. #17 NitroStack 71.2 this agent
  4. #18 Model Context Protocol / MCP 70.7 −0.5
  5. #19 MCP Registry 70.5 −0.7

Bars show each HVTrust score; the tick marks NitroStack’s 71.2.

Where the 71.2 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

71.2 / 100 · 100.0% confidence

NitroStack Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.1 / 25
2.1 below avg 11.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
1.4 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.3 above avg 14.6
AdoptionLog-scaled stars · package downloads
14.8 / 20
3.7 above avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-06
Rank Moved
Rank rose 28 spots (#370 → #342)
2026-10-20
Rank Moved
Rank dropped 18 spots (#331 → #349)
2026-10-13
Rank Moved
Rank rose 23 spots (#340 → #317)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
Compare with another agent
View Protocols & Tool Integration Report missing data
85.3
Activity sub-score · out of 100
#17
In Protocols & Tool Integration

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

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
2.6k
Forks
1.5k
Last Push
2026-11-09
yesterday
Commits (4 wk)
169
Downloads (7d)
97,775
npm
HN mentions (30d)
—
Open Issues
26
Rank Change
▼1
was #344

Analysis

Activity Inputs

85.3 / 100
StarsRepository reach
20.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.8 / 20

Common questions about NitroStack

NitroStack 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 NitroStack publish package provenance?
No published build provenance is currently detected for NitroStack. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does NitroStack have an OpenSSF Scorecard?
NitroStack has an OpenSSF Scorecard score of 3.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 NitroStack actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does NitroStack use?
NitroStack ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are NitroStack's commits signed?
89% of the last 100 commits to NitroStack 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
high confidence
Implemented
NitroStack appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Marketplace
Marketplace plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 NitroStack'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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → marketplace
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Groq
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Supabase

Maintain NitroStack?

For maintainers

HVTrust scores NitroStack 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
Rank 27HVTrust 6Grade 6Score 3Scorecard 1Surface 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-11-06
Rank Moved
Rank rose 28 spots (#370 → #342)
2026-10-20
Rank Moved
Rank dropped 18 spots (#331 → #349)
2026-10-13
Rank Moved
Rank rose 23 spots (#340 → #317)
2026-10-12
Rank Moved
Rank rose 120 spots (#460 → #340)
2026-10-12
HVTrust Changed
HVTrust up 4.3pts (66.2 → 70.5)
2026-10-09
Rank Moved
Rank dropped 10 spots (#441 → #451)
2026-10-08
Rank Moved
Rank dropped 49 spots (#392 → #441)
2026-10-07
Grade Changed
Trust grade C → B
2026-10-07
Rank Moved
Rank rose 189 spots (#581 → #392)
2026-10-07
HVTrust Changed
HVTrust up 5.6pts (62.6 → 68.2)
2026-10-07
Activity Score Changed
Activity score up 12pts (71 → 83)
2026-10-06
Grade Changed
Trust grade B → C
2026-10-06
Rank Moved
Rank dropped 108 spots (#473 → #581)
2026-10-04
Rank Moved
Rank dropped 27 spots (#446 → #473)
2026-10-03
Rank Moved
Rank dropped 39 spots (#407 → #446)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → marketplace
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Groq
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 313 spots (#694 → #381)
2026-09-23
HVTrust Changed
HVTrust up 36.9pts (31.0 → 67.9)
2026-09-22
Newly Listed
First tracked at rank #694
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 14 spots (#341 → #355)
2026-09-09
Rank Moved
Rank rose 57 spots (#401 → #344)
2026-09-08
Rank Moved
Rank dropped 47 spots (#354 → #401)
2026-09-07
Rank Moved
Rank rose 41 spots (#395 → #354)
2026-09-07
Activity Score Changed
Activity score up 7pts (75 → 82)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 600 spots (#989 → #389)
2026-09-05
HVTrust Changed
HVTrust up 22.4pts (42.9 → 65.3)
2026-09-04
Rank Moved
Rank dropped 24 spots (#965 → #989)
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Supabase
2026-09-03
Grade Changed
Trust grade C → D
2026-09-03
Rank Moved
Rank dropped 659 spots (#306 → #965)
2026-09-03
HVTrust Changed
HVTrust down 21.7pts (64.6 → 42.9)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.3/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 616 spots (#923 → #307)
2026-09-01
HVTrust Changed
HVTrust up 26.1pts (38.5 → 64.6)
2026-08-31
Rank Moved
Rank dropped 28 spots (#895 → #923)
2026-08-30
Rank Moved
Rank dropped 38 spots (#857 → #895)
2026-08-29
Rank Moved
Rank dropped 87 spots (#770 → #857)
2026-08-29
Activity Score Changed
Activity score down 9pts (84 → 75)
2026-08-28
Rank Moved
Rank dropped 21 spots (#749 → #770)
2026-08-27
Rank Moved
Rank dropped 22 spots (#727 → #749)
2026-08-26
Rank Moved
Rank dropped 99 spots (#628 → #727)
2026-08-25
Rank Moved
Rank rose 17 spots (#645 → #628)
2026-08-16
Rank Moved
Rank dropped 12 spots (#622 → #634)
GitHub → Website → npm: @nitrostack/core

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

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