@inkandswitch/patchwork-bootloader
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 |
|---|---|---|---|---|
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetches local WASM assets at module load — core bootloader functionality, not telemetry or exfiltration. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): Type-only dev dependency; framework-scoped, not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:resolve.exports | AI (phantom-deps): Config-referenced build utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@automerge/automerge | AI (phantom-deps): Listed as both dep and peer dep; phantom-dep heuristic fires incorrectly here. | ai | |
| phantom-deps | phantom-dep:tinyargs | AI (phantom-deps): Build/config reference; not a direct import concern for this package. | ai | |
| phantom-deps | phantom-dep:service-worker-types | AI (phantom-deps): Type-only package aliased via npm: protocol; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@automerge/automerge-repo | AI (phantom-deps): Listed as both dep and peer dep; phantom-dep heuristic fires incorrectly here. | ai | |
| phantom-deps | phantom-dep:@automerge/vanillajs | AI (phantom-deps): Listed as both dep and peer dep; phantom-dep heuristic fires incorrectly here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 17 / 3 | |
| 0.1.1 | 15 / 3 | |
| 0.0.8 | 15 / 3 | |
| 0.0.6 | 15 / 3 | |
| 0.0.5 | 15 / 3 | |
| 0.0.1 | 8 / 4 |
v0.2.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chee) than the most recent previously approved version (pvh) on 2026-06-02, but chee is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.