@h3ravel/musket
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Runs 'pnpm barrel' (barrelize) to generate barrel files; no network access or arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk used via config/runtime indirection; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs used via config/runtime indirection; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): execa used via config/runtime indirection; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a CLI/dev tool used in scripts and config, not imported directly in source. | ai | |
| phantom-deps | phantom-dep:preferred-pm | AI (phantom-deps): preferred-pm used via config/runtime indirection; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:resolve-from | AI (phantom-deps): resolve-from used via config/runtime indirection; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:radashi | AI (phantom-deps): radashi used via config/runtime indirection; stable false positive for this CLI package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 10 / 11 | |
| 0.10.0 | 10 / 11 | |
| 0.9.1 | 10 / 11 | |
| 0.9.0 | 10 / 11 | |
| 0.6.18 | 10 / 11 | |
| 0.6.17 | 10 / 11 | |
| 0.6.16 | 10 / 11 | |
| 0.6.15 | 10 / 11 | |
| 0.6.14 | 10 / 11 | |
| 0.6.13 | 10 / 11 | |
| 0.6.12 | 11 / 11 | |
| 0.6.9 | 10 / 11 | |
| 0.6.8 | 10 / 11 | |
| 0.6.5 | 10 / 11 | |
| 0.6.3 | 10 / 11 | |
| 0.5.3 | 10 / 11 | |
| 0.5.2 | 10 / 11 | |
| 0.5.1 | 10 / 11 | |
| 0.3.18 | 10 / 11 | |
| 0.3.17 | 10 / 11 | |
| 0.3.16 | 10 / 11 | |
| 0.3.15 | 10 / 11 | |
| 0.3.13 | 10 / 11 | |
| 0.3.10 | 10 / 11 | |
| 0.3.9 | 10 / 11 | |
| 0.3.8 | 10 / 11 | |
| 0.3.5 | 10 / 11 | |
| 0.3.2 | 10 / 11 | |
| 0.3.1 | 10 / 11 | |
| 0.2.1 | 10 / 11 | |
| 0.2.0 | 10 / 11 | |
| 0.1.9 | 10 / 11 | |
| 0.1.7 | 10 / 11 | |
| 0.1.4 | 10 / 11 | |
| 0.1.3 | 10 / 11 | |
| 0.1.1 | 10 / 11 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsScript: pnpm barrel
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.