@aws-amplify/graphql-function-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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is the official AWS Amplify team with strong track record; dormancy reflects normal release cadence for this sub-package. | ai | |
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): graphql-transformer-common is a known Amplify ecosystem package; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.1.19 | 6 / 1 | |
| 3.1.18 | 6 / 1 | |
| 3.1.17 | 6 / 1 | |
| 3.1.16 | 6 / 1 | |
| 3.1.15 | 6 / 1 | |
| 3.1.14 | 6 / 1 | |
| 3.1.13 | 6 / 1 | |
| 3.1.12 | 6 / 1 | |
| 3.1.11 | 6 / 1 | |
| 3.1.10 | 6 / 1 | |
| 3.1.9 | 6 / 1 | |
| 3.1.8 | 6 / 1 | |
| 3.1.7 | 6 / 1 | |
| 3.1.6 | 6 / 1 | |
| 3.1.5 | 6 / 1 | |
| 3.1.4 | 6 / 1 | |
| 3.1.3 | 6 / 1 | |
| 3.1.2 | 6 / 1 | |
| 3.1.1 | 6 / 1 | |
| 3.1.0 | 6 / 1 | |
| 3.0.2 | 6 / 1 | |
| 3.0.1 | 6 / 1 | |
| 3.0.0 | 6 / 1 | |
| 2.1.34 | 6 / 1 |
v3.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.