@peac/capture-node
Node.js durable storage for PEAC capture pipeline (filesystem spool store and dedupe index)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package uses provenance:true; GitHub Actions is the intended publisher for this CI/CD-published package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI with Sigstore SLSA attestation; stable positive signal across versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 1 / 4 | |
| 0.14.5 | 1 / 4 | |
| 0.14.4 | 1 / 4 | |
| 0.14.3 | 1 / 4 | |
| 0.14.2 | 1 / 4 | |
| 0.14.1 | 1 / 4 | |
| 0.14.0 | 1 / 4 | |
| 0.13.4 | 1 / 4 | |
| 0.13.3 | 1 / 4 | |
| 0.13.2 | 1 / 4 | |
| 0.13.1 | 1 / 4 | |
| 0.13.0 | 1 / 4 | |
| 0.12.14 | 1 / 4 | |
| 0.12.13 | 1 / 4 | |
| 0.12.12 | 1 / 4 | |
| 0.12.11 | 1 / 4 | |
| 0.12.10 | 1 / 4 | |
| 0.12.9 | 1 / 4 | |
| 0.12.8 | 1 / 4 | |
| 0.12.7 | 1 / 4 | |
| 0.12.6 | 1 / 4 | |
| 0.12.5 | 1 / 4 | |
| 0.12.4 | 1 / 4 | |
| 0.12.3 | 1 / 4 | |
| 0.12.2 | 1 / 4 | |
| 0.12.1 | 1 / 4 | |
| 0.12.0 | 1 / 4 | |
| 0.11.3 | 1 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.14 | 1 / 4 | |
| 0.10.13 | 1 / 4 | |
| 0.10.12 | 1 / 4 |
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.12
2 findingsThis version was published by a different npm account than previous versions on 2026-04-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.11
2 findingsThis version was published by a different npm account than previous versions on 2026-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.14
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.