@quatrain/queue-gcp
Queue adapter for Google Cloud Platform PubSub
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 | missing-githead | AI (provenance): Established publisher with clean track record; local publish without gitHead is low risk for this package. | ai | |
| dependencies | unvetted-dep:@quatrain/core | AI (dependencies): Same-org monorepo dependency; stable pattern across all @quatrain packages. | ai | |
| dependencies | unvetted-dep:@quatrain/queue | AI (dependencies): Same-org monorepo dependency; stable pattern across all @quatrain packages. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.1.25 | 3 / 11 | |
| 1.1.24 | 3 / 11 | |
| 1.1.23 | 3 / 11 | |
| 1.1.22 | 3 / 11 | |
| 1.1.21 | 3 / 11 | |
| 1.1.20 | 3 / 11 | |
| 1.1.19 | 3 / 11 | |
| 1.1.18 | 3 / 11 | |
| 1.1.17 | 3 / 11 | |
| 1.1.16 | 3 / 11 | |
| 1.1.15 | 3 / 11 | |
| 1.1.14 | 3 / 11 | |
| 1.1.13 | 3 / 11 |
v1.1.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.23
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.