graphql-versioned-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:graphql-mapping-template | AI (dependencies): AWS Amplify monorepo sibling dependency; co-published by the same trusted publisher. | ai | |
| dependencies | unvetted-dep:graphql-transformer-core | AI (dependencies): AWS Amplify monorepo sibling dependency; co-published by the same trusted publisher. | ai | |
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): AWS Amplify monorepo sibling dependency; co-published by the same trusted publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.2.85 | 4 / 1 | |
| 5.2.84 | 4 / 1 | |
| 5.2.83 | 4 / 1 | |
| 5.2.82 | 4 / 1 | |
| 5.2.81 | 4 / 1 | |
| 5.2.80 | 4 / 1 | |
| 5.2.79 | 4 / 1 | |
| 5.2.78 | 4 / 1 |
v5.2.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.