fastq
Fast, in memory work queue
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): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance; repo remains mcollina/fastq. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature stable utility; sporadic publishing is normal. SLSA provenance confirms legitimate CI/CD publish. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.20.1 | 1 / 8 | |
| 1.20.0 | 1 / 8 | |
| 1.19.1 | 1 / 8 | |
| 1.19.0 | 1 / 8 | |
| 1.18.0 | 1 / 8 | |
| 1.17.1 | 1 / 8 |
v1.20.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. 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.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.