@aws-amplify/graphql-sql-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-transformer-common | AI (dependencies): AWS Amplify ecosystem internal dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@aws-amplify/graphql-transformer-core | AI (dependencies): Same AWS Amplify org dependency; expected and stable for this transformer package. | ai | |
| phantom-deps | phantom-dep:@aws-amplify/graphql-model-transformer | AI (phantom-deps): Same-org sibling dep; declared in package.json as a dependency, phantom-dep is a false positive for this monorepo package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.4.23 | 7 / 1 | |
| 0.4.22 | 7 / 1 | |
| 0.4.21 | 7 / 1 | |
| 0.4.20 | 7 / 1 | |
| 0.4.19 | 7 / 1 | |
| 0.4.18 | 7 / 1 | |
| 0.4.17 | 7 / 1 | |
| 0.4.16 | 7 / 1 | |
| 0.4.15 | 7 / 1 | |
| 0.4.14 | 7 / 1 | |
| 0.4.13 | 7 / 1 | |
| 0.4.12 | 7 / 1 | |
| 0.4.11 | 7 / 1 | |
| 0.4.10 | 7 / 1 | |
| 0.4.9 | 7 / 1 | |
| 0.4.8 | 7 / 1 | |
| 0.4.7 | 7 / 1 | |
| 0.4.6 | 7 / 1 | |
| 0.4.5 | 7 / 1 | |
| 0.4.4 | 7 / 1 | |
| 0.4.3 | 7 / 1 | |
| 0.4.2 | 7 / 1 | |
| 0.4.1 | 7 / 1 | |
| 0.4.0 | 7 / 1 | |
| 0.3.9 | 7 / 1 | |
| 0.3.8 | 7 / 1 | |
| 0.3.7 | 7 / 1 | |
| 0.3.6 | 7 / 1 | |
| 0.3.5 | 7 / 1 | |
| 0.3.4 | 7 / 1 | |
| 0.3.3 | 7 / 1 |
v0.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.