← Home

@simpleview/sv-graphql-client

4
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

davidlponsowenallenazqman33svjoshuageorgeyb-svmkes99colin.booenssmith_svaglazebrookrmaynescsarantidessvmikesan789kristian.gonzalezpaul.ridingarkmuntasseractionawesomemcutshallsv-mikaelkorychinn_svleandrodalmassoglbdlfordsloutrel

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Trusted publisher track record; consistent with internal team roster change. ai
maintainer-change maintainer-removed AI (maintainer-change): Paired with added maintainers under same trusted publisher; no behavioral change in diff. ai
publish-pattern dormant-publish AI (publish-pattern): No content changes vs prior approved version; consistent with low-traffic internal package. ai

Versions (showing 4 of 4)

Version Deps Published
4.1.3 9 / 12
4.1.2 9 / 12
4.1.1 9 / 12
4.1.0 9 / 12

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.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.