@nocobase/utils
<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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (axios, ipaddr.js, liquidjs) are all established, well-known packages with no malware history. Addition is consistent with NocoBase framework expansion. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a mainstream templating library; ^4.7.8 pins to a version past known prototype-pollution CVEs. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of Sigstore provenance is consistent across all prior versions and is not a blocking concern. | ai | |
| phantom-deps | phantom-dep:flat-to-nested | AI (phantom-deps): Declared runtime dependency used in config/optional paths; not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:object-path | AI (phantom-deps): Declared runtime dependency used in config/optional paths; not a security concern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): NocoBase is a plugin-based no-code platform; dynamic require() in requireModule.js is an intentional, documented extension mechanism, not a malicious pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @nocobase scoped package with 1022 versions, 29.3k weekly downloads, and 31 approved dependents. Metadata signals are false positives for this well-known OSS project. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 2.0.56 | 15 / 0 | |
| 2.0.55 | 15 / 0 | |
| 2.0.54 | 15 / 0 | |
| 2.0.53 | 15 / 0 | |
| 2.0.52 | 15 / 0 | |
| 2.0.51 | 15 / 0 | |
| 2.0.49 | 15 / 0 | |
| 2.0.46 | 15 / 0 | |
| 2.0.44 | 15 / 0 | |
| 2.0.43 | 15 / 0 | |
| 2.0.42 | 15 / 0 | |
| 2.0.38 | 15 / 0 | |
| 2.0.36 | 13 / 0 | |
| 2.0.33 | 13 / 0 | |
| 2.0.32 | 13 / 0 | |
| 2.0.30 | 13 / 0 | |
| 2.0.28 | 13 / 0 | |
| 2.0.27 | 13 / 0 | |
| 2.0.26 | 13 / 0 | |
| 2.0.25 | 13 / 0 | |
| 2.0.23 | 13 / 0 | |
| 2.0.20 | 13 / 0 | |
| 2.0.17 | 13 / 0 | |
| 2.0.16 | 13 / 0 | |
| 2.0.15 | 13 / 0 | |
| 2.0.12 | 13 / 0 | |
| 2.0.11 | 13 / 0 | |
| 2.0.9 | 13 / 0 | |
| 2.0.8 | 13 / 0 | |
| 2.0.7 | 13 / 0 | |
| 2.0.6 | 13 / 0 | |
| 2.0.5 | 13 / 0 | |
| 2.0.3 | 13 / 0 | |
| 2.0.2 | 13 / 0 | |
| 2.0.1 | 13 / 0 | |
| 2.0.0 | 13 / 0 | |
| 1.9.62 | 12 / 0 | |
| 1.9.56 | 12 / 0 | |
| 1.9.54 | 12 / 0 | |
| 1.9.53 | 12 / 0 | |
| 1.9.52 | 12 / 0 | |
| 1.9.51 | 12 / 0 | |
| 1.9.49 | 12 / 0 | |
| 1.9.47 | 12 / 0 | |
| 1.9.46 | 11 / 0 | |
| 1.9.45 | 11 / 0 | |
| 1.9.44 | 11 / 0 | |
| 1.9.43 | 11 / 0 | |
| 1.9.42 | 11 / 0 | |
| 1.9.41 | 11 / 0 | |
| 1.9.39 | 11 / 0 |
v2.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.