← Home

@aws-amplify/graphql-maps-to-transformer

npm Repository Homepage
7
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

amzn-ossaws-amplify-opsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtime

Keywords

amplifygraphqlcloudformationawsmapstotransformerrefersTo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 7 of 7)

Version Deps Published
4.0.22 5 / 6
4.0.21 5 / 6
4.0.20 5 / 6
4.0.19 5 / 6
3.5.4 5 / 6
3.5.3 5 / 6
3.5.2 5 / 6

v4.0.22

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.

v4.0.21

1 finding
INFO No provenance attestation provenance

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

v4.0.20

1 finding
INFO No provenance attestation provenance

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

v4.0.19

1 finding
INFO No provenance attestation provenance

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

v3.5.4

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.

v3.5.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.

v3.5.2

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.