@strapi/client
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
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 2 / 29 | |
| 1.6.1 | 2 / 24 | |
| 1.6.0 | 2 / 24 | |
| 1.5.0 | 2 / 25 | |
| 1.1.0 | 2 / 24 | |
| 1.0.1 | 2 / 24 | |
| 1.0.0 | 2 / 24 |
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jhoward1994) than the most recent previously approved version (baronvoninternet) on 2025-04-02, but jhoward1994 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (convly) than the most recent previously approved version (baronvoninternet) on 2025-02-17, but convly is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.