@pnp/sp
pnp - provides a fluent api for working with SharePoint REST
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @pnp/sp is the established PnPjs library; no relation to pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @pnp/sp is the established PnPjs library; no relation to qs. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @pnp/sp is the established PnPjs library; no relation to yup. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used for legitimate header key-value mapping, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established PnPjs package; README link dump is documentation-style, not phishing. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.20.0 | 3 / 0 | |
| 4.19.0 | 3 / 0 | |
| 4.18.0 | 3 / 0 | |
| 4.17.0 | 3 / 0 | |
| 4.16.0 | 3 / 0 | |
| 4.15.0 | 3 / 0 | |
| 4.14.0 | 3 / 0 | |
| 4.13.0 | 3 / 0 | |
| 4.12.0 | 3 / 0 | |
| 4.11.0 | 3 / 0 | |
| 4.10.0 | 3 / 0 | |
| 4.9.0 | 3 / 0 | |
| 4.8.0 | 3 / 0 | |
| 4.7.0 | 3 / 0 | |
| 4.6.0 | 3 / 0 | |
| 4.5.0 | 3 / 0 | |
| 4.4.0 | 3 / 0 | |
| 4.3.0 | 3 / 0 | |
| 4.2.0 | 3 / 0 | |
| 4.1.1 | 3 / 0 | |
| 4.1.0 | 3 / 0 | |
| 4.0.1 | 3 / 0 | |
| 4.0.0 | 3 / 0 |
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.