@inkandswitch/patchwork-filesystem
Supply chain provenance
Status for the latest visible version.
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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 2 / 5 | |
| 0.2.3 | 2 / 5 | |
| 0.2.2 | 2 / 5 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.3 | 4 / 3 | |
| 0.1.2 | 4 / 3 | |
| 0.1.1 | 4 / 3 | |
| 0.1.0 | 4 / 3 | |
| 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.2.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chee) on 2026-07-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.