@codebolt/codeboltjs
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:util | AI (phantom-deps): Browser polyfill listed in webpack config; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Browser polyfill for webpack bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:timers | AI (phantom-deps): Browser polyfill for webpack bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:os-browserify | AI (phantom-deps): Browser polyfill for webpack bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Browser polyfill for webpack bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stream-browserify | AI (phantom-deps): Browser polyfill for webpack bundle; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): CLI tooling dep; referenced in config, stable for this package. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): CLI tooling dep; referenced in config, stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): Type-only package loaded by convention; false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 13 / 17 | |
| 5.1.40 | 15 / 17 | |
| 5.1.39 | 15 / 17 | |
| 5.1.38 | 15 / 17 | |
| 5.1.37 | 15 / 17 | |
| 5.1.36 | 15 / 17 | |
| 5.1.35 | 15 / 17 | |
| 5.1.34 | 15 / 17 | |
| 5.1.32 | 15 / 17 | |
| 5.1.31 | 15 / 17 | |
| 5.1.30 | 14 / 17 | |
| 5.1.29 | 14 / 17 | |
| 5.1.28 | 14 / 17 | |
| 5.1.27 | 14 / 17 | |
| 5.1.26 | 14 / 17 | |
| 5.1.25 | 14 / 17 | |
| 5.1.24 | 14 / 17 | |
| 5.1.23 | 14 / 17 | |
| 5.1.22 | 14 / 17 | |
| 5.1.21 | 14 / 17 | |
| 5.1.20 | 14 / 17 | |
| 5.1.19 | 14 / 17 | |
| 5.1.18 | 14 / 17 | |
| 5.1.17 | 14 / 17 | |
| 5.1.16 | 14 / 17 | |
| 5.1.15 | 14 / 17 | |
| 5.1.14 | 14 / 17 | |
| 5.1.13 | 14 / 17 | |
| 5.1.12 | 14 / 17 | |
| 5.1.10 | 14 / 17 | |
| 5.0.9 | 13 / 17 | |
| 5.0.8 | 13 / 17 | |
| 5.0.7 | 13 / 17 | |
| 5.0.6 | 13 / 17 | |
| 5.0.5 | 13 / 17 | |
| 5.0.4 | 13 / 17 | |
| 5.0.3 | 13 / 17 | |
| 5.0.2 | 13 / 14 | |
| 5.0.1 | 13 / 14 | |
| 5.0.0 | 13 / 14 | |
| 4.0.3 | 13 / 14 | |
| 4.0.2 | 13 / 14 |
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.