← Home

@pnp/sp

npm Repository Homepage

pnp - provides a fluent api for working with SharePoint REST

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

patrick-rodgerswaldekmvesajuvonenjansenbeofficedevpnpstfbauergarry.trinderappieschotarjunumenoneliostruyf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 8 of 8)

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

v4.20.0

1 finding
LOW No provenance attestation provenance

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

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

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

v4.17.0

1 finding
LOW No provenance attestation provenance

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

v4.16.0

1 finding
LOW No provenance attestation provenance

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

v4.15.0

1 finding
LOW No provenance attestation provenance

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

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

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