@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, 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:@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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 17 / 4 | |
| 2.4.2 | 17 / 4 | |
| 2.4.1 | 17 / 4 | |
| 2.4.0 | 17 / 4 | |
| 2.3.4 | 17 / 4 | |
| 2.3.3 | 17 / 4 | |
| 2.3.2 | 17 / 4 | |
| 2.3.1 | 17 / 4 | |
| 2.3.0 | 17 / 4 | |
| 2.2.7 | 16 / 4 | |
| 2.2.6 | 16 / 4 | |
| 2.2.5 | 16 / 4 | |
| 2.2.4 | 16 / 4 | |
| 2.2.3 | 16 / 4 | |
| 2.2.2 | 16 / 5 | |
| 2.2.1 | 16 / 5 | |
| 2.2.0 | 16 / 5 | |
| 2.1.8 | 16 / 5 | |
| 2.1.7 | 16 / 5 | |
| 2.1.6 | 15 / 5 | |
| 2.1.5 | 15 / 5 | |
| 2.1.4 | 15 / 5 | |
| 2.1.3 | 15 / 5 | |
| 2.1.2 | 15 / 5 | |
| 2.1.1 | 15 / 5 | |
| 2.1.0 | 15 / 5 | |
| 2.0.1 | 13 / 5 | |
| 2.0.0 | 13 / 5 | |
| 1.8.5 | 13 / 4 | |
| 1.8.4 | 13 / 4 | |
| 1.8.3 | 13 / 4 |
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.