@aws-amplify/graphql-schema-generator
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pg | AI (phantom-deps): pg is a declared runtime dep used as an optional knex DB driver; not directly imported in source but legitimately bundled. | ai | |
| phantom-deps | phantom-dep:mysql2 | AI (phantom-deps): mysql2 is a declared runtime dep used as an optional knex DB driver; not directly imported in source but legitimately bundled. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.11.16 | 16 / 2 | |
| 0.11.15 | 16 / 2 | |
| 0.11.14 | 16 / 2 | |
| 0.11.13 | 16 / 2 | |
| 0.11.4 | 16 / 2 | |
| 0.11.2 | 16 / 2 | |
| 0.11.1 | 16 / 2 | |
| 0.11.0 | 16 / 2 | |
| 0.10.6 | 16 / 2 | |
| 0.10.5 | 16 / 2 | |
| 0.10.4 | 16 / 2 | |
| 0.10.3 | 16 / 2 | |
| 0.10.2 | 16 / 2 | |
| 0.10.1 | 16 / 2 | |
| 0.10.0 | 16 / 2 | |
| 0.9.4 | 16 / 2 | |
| 0.9.3 | 16 / 2 | |
| 0.9.2 | 16 / 2 | |
| 0.9.1 | 16 / 2 | |
| 0.9.0 | 16 / 2 | |
| 0.8.6 | 16 / 2 |
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.