← Home

graphql-transformer-core

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-ossaws-amplify-opsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtimemlabieniecelorzafe

Keywords

graphqlcloudformationawsamplify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): AWS-owned org maintainer rotation, consistent with trusted publisher account. ai
publish-pattern dormant-publish AI (publish-pattern): Likely registry-import artifact; package has continuous long-term npm history. ai
bogus-package bogus-package AI (bogus-package): Legitimate AWS Amplify monorepo package; mass-production and README signals are false positives for this publisher. ai
dependencies unvetted-dep:graphql-transformer-common AI (dependencies): graphql-transformer-common is a sibling AWS Amplify package; stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
9.0.7 7 / 5
9.0.6 7 / 5
9.0.5 7 / 5
9.0.4 7 / 5
9.0.3 7 / 5
9.0.2 7 / 5
9.0.1 7 / 5
9.0.0 7 / 5
8.2.18 7 / 5

v9.0.5

1 finding
LOW No provenance attestation provenance

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

v9.0.4

1 finding
LOW No provenance attestation provenance

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

v9.0.3

1 finding
LOW No provenance attestation provenance

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

v9.0.2

1 finding
LOW No provenance attestation provenance

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

v9.0.1

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.

v9.0.0

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.