@pbvision/cloud-run-service
fastify-firestore-service Web Framework on Cloud Run
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): Transition to GitHub Actions CI/CD publishing with SLSA attestation; provenance direction is IMPROVED, not a takeover signal. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package (@pbvision); no provenance attestation is consistent across versions and not indicative of malice. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.0.47 | 4 / 20 | |
| 0.0.46 | 4 / 20 | |
| 0.0.45 | 4 / 20 | |
| 0.0.44 | 4 / 20 | |
| 0.0.43 | 4 / 20 | |
| 0.0.42 | 4 / 20 | |
| 0.0.41 | 4 / 20 | |
| 0.0.40 | 4 / 20 | |
| 0.0.39 | 4 / 20 | |
| 0.0.38 | 4 / 20 | |
| 0.0.37 | 4 / 20 | |
| 0.0.36 | 4 / 20 | |
| 0.0.35 | 4 / 20 | |
| 0.0.34 | 4 / 20 | |
| 0.0.33 | 4 / 20 | |
| 0.0.32 | 4 / 20 | |
| 0.0.31 | 4 / 20 | |
| 0.0.30 | 4 / 20 | |
| 0.0.29 | 3 / 19 | |
| 0.0.28 | 3 / 19 | |
| 0.0.27 | 3 / 18 | |
| 0.0.26 | 3 / 18 | |
| 0.0.25 | 3 / 18 | |
| 0.0.24 | 3 / 18 | |
| 0.0.23 | 3 / 18 | |
| 0.0.22 | 3 / 18 | |
| 0.0.21 | 3 / 18 | |
| 0.0.20 | 3 / 18 | |
| 0.0.13 | 3 / 18 | |
| 0.0.5 | 3 / 18 | |
| 0.0.2 | 3 / 18 | |
| 0.0.1 | 3 / 18 |
v0.0.47
2 findingsThis version was published by a different npm account than previous versions on 2026-07-05. 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.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.