@aws-amplify/graphql-maps-to-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 | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is the official AWS Amplify npm account with a strong track record; dormancy reflects project cadence, not takeover risk. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.0.23 | 5 / 6 | |
| 4.0.22 | 5 / 6 | |
| 4.0.21 | 5 / 6 | |
| 4.0.20 | 5 / 6 | |
| 4.0.19 | 5 / 6 | |
| 4.0.18 | 5 / 6 | |
| 4.0.17 | 5 / 6 | |
| 4.0.16 | 5 / 6 | |
| 4.0.15 | 5 / 6 | |
| 4.0.14 | 5 / 6 | |
| 4.0.13 | 5 / 6 | |
| 4.0.12 | 5 / 6 | |
| 4.0.11 | 5 / 6 | |
| 4.0.10 | 5 / 6 | |
| 4.0.9 | 5 / 6 | |
| 4.0.8 | 5 / 6 | |
| 4.0.7 | 5 / 6 | |
| 4.0.6 | 5 / 6 | |
| 4.0.5 | 5 / 6 | |
| 4.0.4 | 5 / 6 | |
| 4.0.3 | 5 / 6 | |
| 4.0.2 | 5 / 6 | |
| 4.0.1 | 5 / 6 | |
| 4.0.0 | 5 / 6 | |
| 3.5.4 | 5 / 6 | |
| 3.5.3 | 5 / 6 | |
| 3.5.2 | 5 / 6 |
v4.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.