@aws-amplify/graphql-auth-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): graphql-transformer-common is a known Amplify ecosystem package; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify packages consistently publish without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.2.9 | 10 / 6 | |
| 4.2.8 | 10 / 6 | |
| 4.2.7 | 10 / 6 | |
| 4.2.6 | 10 / 6 | |
| 4.2.5 | 10 / 6 | |
| 4.2.4 | 10 / 6 | |
| 4.2.3 | 10 / 6 | |
| 4.2.2 | 10 / 6 | |
| 4.2.1 | 10 / 6 | |
| 4.2.0 | 10 / 6 | |
| 4.1.12 | 10 / 6 | |
| 4.1.11 | 10 / 6 | |
| 4.1.10 | 10 / 6 | |
| 4.1.9 | 10 / 6 | |
| 4.1.8 | 10 / 6 | |
| 4.1.7 | 10 / 6 | |
| 4.1.6 | 10 / 6 | |
| 4.1.5 | 10 / 6 | |
| 4.1.4 | 10 / 6 | |
| 4.1.3 | 10 / 6 | |
| 4.1.2 | 10 / 6 | |
| 4.1.1 | 10 / 6 | |
| 4.1.0 | 10 / 6 | |
| 4.0.1 | 10 / 6 | |
| 4.0.0 | 10 / 6 | |
| 3.6.16 | 10 / 6 | |
| 3.6.15 | 10 / 6 | |
| 3.6.14 | 10 / 6 |
v4.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.