graphql-connection-transformer
2
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.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): aws-amplify-data-runtime is the AWS Amplify team consolidation account; consistent with org-level maintainer rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are individual AWS employees replaced by team account; expected for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): AWS Amplify packages are published in coordinated batches; long gaps between releases are normal for this ecosystem. | ai | |
| phantom-deps | phantom-dep:graphql-key-transformer | AI (phantom-deps): Sibling monorepo package; declared as peer/config dep, stable false positive for this package. | ai |
v5.2.85
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.80
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.