graphql-function-transformer
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): AWS Amplify monorepo package; provenance not used across this publisher's releases. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.3.76 | 5 / 0 | |
| 3.3.75 | 5 / 0 | |
| 3.3.74 | 5 / 0 | |
| 3.3.73 | 5 / 0 | |
| 3.3.72 | 5 / 0 | |
| 3.3.71 | 5 / 0 | |
| 3.3.70 | 5 / 0 | |
| 3.3.69 | 5 / 0 |
v3.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.