@inkandswitch/patchwork-filesystem
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): chee is an established publisher (23 approved) within the same Ink & Switch org; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@automerge/automerge | AI (phantom-deps): Declared in dependencies and used; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type definitions loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): Framework-scoped type definitions loaded by convention; stable for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 4 / 3 | |
| 0.0.7 | 4 / 3 | |
| 0.0.6 | 4 / 3 | |
| 0.0.5 | 4 / 3 | |
| 0.0.4 | 4 / 3 | |
| 0.0.3 | 6 / 1 | |
| 0.0.2 | 6 / 1 | |
| 0.0.1 | 6 / 1 |
v0.0.8
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-05-27, 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.0.7
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 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
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.