graphql-transformer-common
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): Org-internal maintainer transition on official AWS package, no code changes. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with added org maintainer, consistent with team handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No content diff; dormancy explained by monorepo release cadence. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.1.4 | 4 / 1 | |
| 5.1.3 | 4 / 1 | |
| 5.1.2 | 4 / 1 | |
| 5.1.1 | 4 / 1 | |
| 5.1.0 | 4 / 1 | |
| 5.0.1 | 4 / 1 | |
| 5.0.0 | 4 / 1 |
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.