@aws-amplify/graphql-predictions-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 npm account with strong track record; dormancy likely reflects repo restructuring, not takeover. | ai | |
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): graphql-transformer-common is a long-standing Amplify ecosystem dependency pinned to a specific version; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.0.23 | 6 / 2 | |
| 3.0.22 | 6 / 2 | |
| 3.0.21 | 6 / 2 | |
| 3.0.20 | 6 / 2 | |
| 3.0.19 | 6 / 2 | |
| 3.0.18 | 6 / 2 | |
| 3.0.17 | 6 / 2 | |
| 3.0.16 | 6 / 2 | |
| 3.0.15 | 6 / 2 | |
| 3.0.14 | 6 / 2 | |
| 3.0.13 | 6 / 2 | |
| 3.0.12 | 6 / 2 | |
| 3.0.11 | 6 / 2 | |
| 3.0.10 | 6 / 2 | |
| 3.0.9 | 6 / 2 | |
| 3.0.8 | 6 / 2 | |
| 3.0.7 | 6 / 2 | |
| 3.0.6 | 6 / 2 | |
| 3.0.5 | 6 / 2 | |
| 3.0.4 | 6 / 2 | |
| 3.0.3 | 6 / 2 | |
| 3.0.2 | 6 / 2 | |
| 3.0.1 | 6 / 2 | |
| 3.0.0 | 6 / 2 | |
| 2.2.2 | 6 / 2 |
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
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.