box-node-sdk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib-esm/bundle.js | AI (source-diff): WebAssembly hash implementations bundled from hash-wasm; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript type package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/bluebird | AI (phantom-deps): TypeScript type package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Used in config/validation tooling, not direct runtime import; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard SDK utility for decoding API responses; not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used implicitly by TypeScript compiled output. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-to-base64 conversion utility in official Box SDK; benign data handling. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 10.11.1 | 8 / 14 | |
| 10.11.0 | 8 / 14 | |
| 10.10.0 | 8 / 14 | |
| 10.9.0 | 8 / 14 | |
| 10.8.0 | 8 / 14 | |
| 10.7.0 | 8 / 14 | |
| 10.6.0 | 8 / 14 | |
| 4.11.2 | 17 / 34 | |
| 4.11.1 | 17 / 34 | |
| 4.11.0 | 17 / 34 | |
| 4.10.0 | 17 / 34 | |
| 4.9.0 | 17 / 34 | |
| 4.8.0 | 17 / 34 | |
| 4.7.0 | 17 / 34 | |
| 4.6.0 | 17 / 34 |
v10.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.