Nocobase
Website
NocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of production-proven infrastructure and a WYSIWYG no-code interface, so you get both speed and reliability.
Is Nocobase safe? Promising trust profile, but some evidence still deserves review.
Compare Nocobase
How does it stack up against its Workflow Platforms neighbours?
Pick any agent to compare →In detail: Nocobase scores 65.6/100 (Grade B), ranked #493 of 1378 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 4.3/10; 63% of recent commits are signed; no published advisory affects its latest release (nocobase); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How Nocobase 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.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 80.3 A · #5 of 26
- Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dangerous-Workflow 0 +9.8 → 75.4 B · #7 of 26
- Sign every commit63% signed today +1.9 → 67.5 B · #8 of 26
Chain of custody
Scanners check what the code says. This traces who ships Nocobase 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.
-
Source Partly signed
github.com/nocobase/nocobase, NOASSERTION, last pushed 2026-10-17. 63% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 8CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 9Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked, not attested
- npm nocobase Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: nocobase 0.1.5. No published advisory affects it (OSV, checked 2026-10-16).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Nocobase.
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 Nocobase’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.
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 Nocobase compares in Workflow Platforms
- #8 Hatchet 67.2 +1.6
- #9 Airbyte 66.8 +1.2
- #10 Nocobase 65.6 this agent
- #11 Sim 65.1 −0.5
- #12 Conductor 65.0 −0.6
Bars show each HVTrust score; the tick marks Nocobase’s 65.6.
Where the 65.6 comes from
HVTrust dimensions vs the Workflow Platforms average
65.6 / 100 · 100.0% confidenceNocobase Workflow Platforms average (26 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
91.5 / 100Common questions about Nocobase
Does Nocobase publish package provenance?
Does Nocobase have an OpenSSF Scorecard?
Is Nocobase actively maintained?
What license does Nocobase use?
Are Nocobase's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Nocobase?
For maintainers
HVTrust scores Nocobase 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/nocobase)
<a href="https://hvtracker.net/agents/nocobase"><img src="https://hvtracker.net/badge/nocobase.svg" alt="HVTrust"></a>
Other agents in Workflow Platforms
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