← Home

graphql-elasticsearch-transformer

npm Repository Homepage
4
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-runtimemlabieniecelorzafekaustavghosh06

Keywords

graphqlappsyncaws

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 sibling package in the aws-amplify/amplify-category-api monorepo; stable false positive for this package. ai
provenance no-provenance AI (provenance): AWS Amplify monorepo package; provenance not attested but publisher is well-established with strong track record. ai

Versions (showing 4 of 4)

Version Deps Published
5.2.89 5 / 3
5.2.87 5 / 3
5.2.86 5 / 3
5.2.81 5 / 3

v5.2.89

1 finding
INFO No provenance attestation provenance

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

v5.2.87

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.

v5.2.86

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.

v5.2.81

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.