@aws-amplify/graphql-transformer-core No license 25 versions

@aws-amplify/graphql-transformer-core

npm Repository Homepage

25

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-runtime

Keywords

graphqlcloudformationawsamplifytransformer

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:hjson	AI (phantom-deps): hjson is a declared runtime dep used via config files; phantom-dep heuristic is a false positive here.	ai	2026/05/26
phantom-deps	phantom-dep:fs-extra	AI (phantom-deps): fs-extra is a declared runtime dep; phantom-dep heuristic is a false positive for this package.	ai	2026/05/26

Versions (showing 25 of 25)

Version	Deps	Published
3.6.1	11 / 6	2026-07-13
3.6.0	11 / 6	2026-07-01
3.5.1	11 / 6	2026-03-24
3.5.0	11 / 6	2026-02-05
3.4.4	11 / 6	2025-06-09
3.4.3	11 / 6	2025-04-17
3.4.2	11 / 6	2025-04-09
3.4.1	11 / 6	2025-03-06
3.4.0	11 / 6	2025-02-26
3.3.6	11 / 6	2025-02-07
3.3.5	11 / 6	2025-01-30
3.3.4	11 / 6	2025-01-16
3.3.3	11 / 6	2024-12-23
3.3.2	12 / 6	2024-12-17
3.3.1	11 / 6	2024-11-14
3.3.0	11 / 6	2024-11-08
3.2.2	11 / 6	2024-10-28
3.2.1	11 / 6	2024-10-17
3.2.0	11 / 6	2024-10-10
3.1.2	11 / 6	2024-10-01
3.1.1	11 / 6	2024-09-16
3.1.0	11 / 6	2024-09-06
3.0.1	11 / 6	2024-08-28
3.0.0	11 / 6	2024-08-20
2.11.3	11 / 6	2025-11-19

v3.6.1

1 finding

LOW No provenance attestation provenance

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

v3.6.0

1 finding

LOW No provenance attestation provenance

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

v3.4.3

1 finding

LOW No provenance attestation provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.4.1

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.6

1 finding

LOW No provenance attestation provenance

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

v3.3.5

1 finding

LOW No provenance attestation provenance

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

v3.3.4

1 finding

LOW No provenance attestation provenance

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

v3.3.3

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

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