@aws-amplify/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is the official AWS Amplify team with strong track record; dormancy reflects normal release cadence for this sub-package. | ai | |
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): graphql-transformer-common is a known Amplify ecosystem package; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.1.18 | 6 / 1 | |
| 3.1.17 | 6 / 1 | |
| 3.1.16 | 6 / 1 | |
| 2.1.34 | 6 / 1 |
v3.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.