@nocobase/sdk
<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): NocoBase is a large monorepo; sub-packages like @nocobase/sdk routinely lack standalone repo URLs, keywords, and verbose READMEs. 961 versions and 1439 days of history confirm legitimacy. | ai | |
| provenance | no-provenance | AI (provenance): NocoBase packages have not historically published with Sigstore provenance; absence is consistent across all 961 versions and is not a security risk given other trust signals. | ai |
Versions (showing 25 of 133)
| Version | Deps | Published |
|---|---|---|
| 1.9.22 | 2 / 1 | |
| 1.9.21 | 2 / 1 | |
| 1.9.20 | 2 / 1 | |
| 1.9.19 | 2 / 1 | |
| 1.9.18 | 2 / 1 | |
| 1.9.17 | 2 / 1 | |
| 1.9.16 | 2 / 1 | |
| 1.9.15 | 2 / 1 | |
| 1.9.14 | 2 / 1 | |
| 1.9.13 | 2 / 1 | |
| 1.9.12 | 2 / 1 | |
| 1.9.11 | 2 / 1 | |
| 1.9.10 | 2 / 1 | |
| 1.9.9 | 2 / 1 | |
| 1.9.8 | 2 / 1 | |
| 1.9.7 | 2 / 1 | |
| 1.9.6 | 2 / 1 | |
| 1.9.5 | 2 / 1 | |
| 1.9.4 | 2 / 1 | |
| 1.9.3 | 2 / 1 | |
| 1.9.2 | 2 / 1 | |
| 1.9.1 | 2 / 1 | |
| 1.9.0 | 2 / 1 | |
| 1.8.33 | 2 / 1 | |
| 1.8.32 | 2 / 1 |
v1.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.