@aws-amplify/graphql-relational-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): Internal Amplify ecosystem dependency; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-transformer-core | AI (dependencies): Internal Amplify ecosystem dependency; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.1.13 | 9 / 1 | |
| 3.1.12 | 9 / 1 | |
| 3.1.11 | 9 / 1 | |
| 2.5.20 | 9 / 1 |
v3.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
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.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.