@nocobase/telemetry
nocobase telemetry library
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 open-source monorepo; README link dumps and missing keywords are a cosmetic issue, not indicative of spam or phishing for this established package. | ai | |
| dependencies | unvetted-dep:@nocobase/utils | AI (dependencies): @nocobase/utils is a sibling package in the same NocoBase monorepo, always published at the same version. Dependency is expected and legitimate. | ai |
Versions (showing 31 of 133)
| Version | Deps | Published |
|---|---|---|
| 1.9.28 | 8 / 0 | |
| 1.9.27 | 8 / 0 | |
| 1.9.26 | 8 / 0 | |
| 1.9.25 | 8 / 0 | |
| 1.9.24 | 8 / 0 | |
| 1.9.23 | 8 / 0 | |
| 1.9.22 | 8 / 0 | |
| 1.9.21 | 8 / 0 | |
| 1.9.20 | 8 / 0 | |
| 1.9.19 | 8 / 0 | |
| 1.9.18 | 8 / 0 | |
| 1.9.17 | 8 / 0 | |
| 1.9.16 | 8 / 0 | |
| 1.9.15 | 8 / 0 | |
| 1.9.14 | 8 / 0 | |
| 1.9.13 | 8 / 0 | |
| 1.9.12 | 8 / 0 | |
| 1.9.11 | 8 / 0 | |
| 1.9.10 | 8 / 0 | |
| 1.9.9 | 8 / 0 | |
| 1.9.8 | 8 / 0 | |
| 1.9.7 | 8 / 0 | |
| 1.9.6 | 8 / 0 | |
| 1.9.5 | 8 / 0 | |
| 1.9.4 | 8 / 0 | |
| 1.9.3 | 8 / 0 | |
| 1.9.2 | 8 / 0 | |
| 1.9.1 | 8 / 0 | |
| 1.9.0 | 8 / 0 | |
| 1.8.33 | 8 / 0 | |
| 1.8.32 | 8 / 0 |
v1.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.