device-file
Device only file
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:b4a | AI (dependencies): b4a is a standard Holepunch/mafintosh ecosystem utility for buffer handling, consistently used across their packages. Not a real risk for this publisher. | ai | |
| phantom-deps | phantom-dep:bare-fs | AI (phantom-deps): bare-fs is declared in dependencies and used via the package.json imports map for Bare runtime conditional resolution — a legitimate dual-runtime pattern, not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:bare-path | AI (phantom-deps): bare-path is declared in dependencies and used via the package.json imports map for Bare runtime conditional resolution — a legitimate dual-runtime pattern, not a true phantom dep. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 6 / 4 | |
| 2.3.0 | 6 / 4 | |
| 2.2.0 | 6 / 4 | |
| 2.1.3 | 6 / 4 | |
| 2.1.2 | 6 / 4 | |
| 2.1.1 | 6 / 4 | |
| 2.1.0 | 6 / 4 | |
| 2.0.7 | 6 / 4 | |
| 2.0.6 | 6 / 4 | |
| 2.0.5 | 5 / 4 | |
| 2.0.4 | 5 / 4 | |
| 2.0.3 | 5 / 4 | |
| 2.0.2 | 5 / 4 | |
| 2.0.1 | 4 / 4 | |
| 2.0.0 | 4 / 4 |
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.