bolt
> Super-powered JavaScript project management
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 (chunkd, ci-parallel-vars, detect-newline) are small, well-known utility packages appropriate for bolt's monorepo tooling use case. No malicious signals. | ai | |
| provenance | no-provenance | AI (provenance): bolt is a mature package (5328 days old) predating Sigstore provenance; absence of attestation is expected and not a meaningful risk signal for this package. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): bolt is a well-established monorepo/workspace tool (boltpkg) with no relation to 'got'. Levenshtein proximity is coincidental; no impersonation intent. | ai | |
| npm-metadata | url-dep:meow | AI (npm-metadata): Pinned to a specific commit hash of meow by the legitimate author. Deterministic and intentional; acceptable for this established package. | ai | |
| provenance | publisher-changed | AI (provenance): thejameskyle is the listed author in package.json and has a strong publishing track record; the 2019 transition from lbatchelor back to the original author is a legitimate handoff. | ai | |
| phantom-deps | phantom-dep:yarn | AI (phantom-deps): bolt wraps yarn as a subprocess; yarn is a legitimate runtime dep referenced in config/tooling, not directly imported in JS. Stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): thejameskyle (James Kyle) is a well-known OSS developer (Babel, Flow). The spam flag is a false positive; bolt is a legitimate, established monorepo tool with 79 approved versions. | ai | |
| phantom-deps | phantom-dep:find-up | AI (phantom-deps): find-up is a legitimate runtime dependency used indirectly; phantom-dep finding is a false positive for this package's architecture. | ai | |
| phantom-deps | phantom-dep:is-glob | AI (phantom-deps): is-glob is a legitimate runtime dependency used indirectly; phantom-dep finding is a false positive for this package's architecture. | ai | |
| phantom-deps | phantom-dep:read-pkg | AI (phantom-deps): read-pkg is a legitimate runtime dependency used indirectly; phantom-dep finding is a false positive for this package's architecture. | ai | |
| dependencies | unvetted-dep:yarn | AI (dependencies): yarn is a well-known package manager; bolt intentionally depends on it as it wraps yarn workspaces functionality. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.24.10 | 33 / 16 | |
| 0.24.9 | 33 / 16 | |
| 0.24.8 | 33 / 16 | |
| 0.24.7 | 33 / 16 | |
| 0.24.6 | 33 / 16 | |
| 0.24.5 | 33 / 16 | |
| 0.24.4 | 33 / 16 | |
| 0.24.3 | 33 / 16 | |
| 0.24.2 | 33 / 16 | |
| 0.24.1 | 33 / 16 | |
| 0.24.0 | 33 / 16 | |
| 0.23.6 | 33 / 16 | |
| 0.23.5 | 33 / 16 | |
| 0.23.4 | 33 / 16 | |
| 0.23.3 | 33 / 16 | |
| 0.23.2 | 33 / 16 | |
| 0.23.1 | 33 / 16 | |
| 0.22.6 | 32 / 16 | |
| 0.22.5 | 32 / 16 | |
| 0.22.4 | 32 / 16 | |
| 0.22.3 | 30 / 16 | |
| 0.22.2 | 30 / 16 | |
| 0.22.1 | 30 / 16 | |
| 0.22.0 | 30 / 16 | |
| 0.21.2 | 30 / 16 | |
| 0.21.1 | 30 / 16 | |
| 0.21.0 | 30 / 16 | |
| 0.20.7 | 30 / 16 | |
| 0.20.6 | 30 / 16 | |
| 0.20.5 | 30 / 16 | |
| 0.20.4 | 30 / 16 | |
| 0.20.3 | 30 / 16 | |
| 0.20.2 | 30 / 16 | |
| 0.20.1 | 30 / 16 | |
| 0.20.0 | 30 / 15 | |
| 0.19.3 | 30 / 15 | |
| 0.19.2 | 29 / 15 | |
| 0.19.1 | 29 / 15 | |
| 0.19.0 | 29 / 15 | |
| 0.18.4 | 29 / 15 | |
| 0.18.3 | 27 / 15 | |
| 0.18.2 | 27 / 15 | |
| 0.18.1 | 27 / 15 | |
| 0.18.0 | 27 / 15 | |
| 0.17.7 | 24 / 15 | |
| 0.17.6 | 22 / 15 | |
| 0.17.5 | 22 / 15 | |
| 0.17.4 | 22 / 15 | |
| 0.17.2 | 22 / 15 | |
| 0.17.1 | 22 / 15 | |
| 0.17.0 | 22 / 15 |
v0.24.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.24.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.24.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-01-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.23.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-19. This could indicate a legitimate maintainer transition or an account compromise.
v0.20.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.20.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-12-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-12-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-12-22. This could indicate a legitimate maintainer transition or an account compromise.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.17.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.