@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 20 of 20)
| 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 | |
| 1.1.12 | 3 / 11 | |
| 1.1.11 | 3 / 11 | |
| 1.1.10 | 3 / 11 | |
| 1.1.9 | 3 / 11 | |
| 1.1.8 | 3 / 11 | |
| 1.1.7 | 3 / 11 | |
| 1.1.6 | 3 / 11 |
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.