@faststore/graphql-utils
GraphQL utilities
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 publisher is expected for vtex/faststore monorepo; SLSA attestation confirms legitimate CI build. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.99.4 | 0 / 1 | |
| 3.99.1 | 0 / 1 | |
| 3.99.0 | 0 / 1 | |
| 3.98.0 | 0 / 1 | |
| 3.97.0 | 0 / 1 | |
| 3.96.0 | 0 / 1 | |
| 3.95.0 | 0 / 1 | |
| 3.94.0 | 0 / 1 | |
| 3.93.0 | 0 / 1 | |
| 3.92.0 | 0 / 1 | |
| 3.91.2 | 0 / 1 | |
| 3.89.2 | 0 / 1 | |
| 3.81.0 | 0 / 1 | |
| 3.80.0 | 0 / 1 | |
| 3.56.1 | 0 / 1 | |
| 3.50.3 | 0 / 1 | |
| 3.49.1 | 0 / 1 | |
| 3.45.0 | 0 / 1 | |
| 3.38.3 | 0 / 1 | |
| 3.28.0 | 0 / 1 | |
| 3.26.0 | 0 / 1 | |
| 3.22.2 | 0 / 1 | |
| 3.15.3 | 0 / 1 | |
| 3.15.0 | 0 / 1 | |
| 3.14.2 | 0 / 1 | |
| 3.13.1 | 0 / 1 | |
| 3.11.3 | 0 / 1 | |
| 3.9.2 | 0 / 3 | |
| 3.9.0 | 0 / 5 | |
| 3.5.0 | 0 / 5 | |
| 3.4.4 | 0 / 5 | |
| 3.4.3 | 0 / 5 | |
| 3.4.2 | 0 / 5 | |
| 3.4.1 | 0 / 5 | |
| 3.1.3 | 0 / 5 | |
| 3.0.160 | 0 / 5 | |
| 3.0.152 | 0 / 5 | |
| 3.0.150 | 0 / 5 | |
| 3.0.135 | 0 / 5 | |
| 3.0.134 | 0 / 5 | |
| 3.0.131 | 0 / 5 | |
| 3.0.116 | 0 / 5 | |
| 3.0.110 | 0 / 5 | |
| 3.0.109 | 0 / 5 | |
| 3.0.97 | 0 / 5 | |
| 3.0.95 | 0 / 5 | |
| 3.0.94 | 0 / 5 | |
| 3.0.88 | 0 / 5 | |
| 3.0.68 | 0 / 5 | |
| 3.0.66 | 0 / 5 | |
| 3.0.63 | 0 / 5 | |
| 3.0.54 | 0 / 5 | |
| 3.0.47 | 0 / 5 |
v3.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.