@aws-amplify/graphql-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:@aws-amplify/graphql-sql-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-auth-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-http-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-transformer-core | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-index-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-model-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-maps-to-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-function-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-validate-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-generation-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-relational-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-searchable-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-predictions-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-conversation-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-default-value-transformer | AI (dependencies): Sibling AWS Amplify monorepo package from same trusted publisher. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.4.2 | 17 / 4 | |
| 2.4.1 | 17 / 4 | |
| 2.4.0 | 17 / 4 | |
| 2.3.4 | 17 / 4 | |
| 1.8.5 | 13 / 4 | |
| 1.8.4 | 13 / 4 | |
| 1.8.3 | 13 / 4 |
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.