← Home

@aws-amplify/graphql-generator

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

amzn-ossundefobjaws-amplify-opsthaddmtmattsb42-awsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtime

Keywords

graphqlappsyncaws

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Deps are established graphql-codegen/tools packages, consistent with package's stated function. ai
publish-pattern dormant-publish AI (publish-pattern): Monorepo package with staggered release cadence; publisher has long clean track record. ai
phantom-deps phantom-dep:@graphql-tools/apollo-engine-loader AI (phantom-deps): Declared as a runtime dep in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
0.5.3 11 / 1
0.5.2 11 / 1
0.5.1 11 / 1
0.5.0 11 / 1
0.4.7 8 / 1
0.4.6 8 / 1
0.4.5 8 / 1
0.4.4 8 / 1
0.4.3 8 / 1

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.