graphql-connection-transformer
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.2.85 | 7 / 0 | |
| 5.2.84 | 7 / 0 | |
| 5.2.83 | 7 / 0 | |
| 5.2.82 | 7 / 0 | |
| 5.2.81 | 7 / 0 | |
| 5.2.80 | 7 / 0 | |
| 5.2.79 | 7 / 0 | |
| 5.2.78 | 7 / 0 |
v5.2.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.