@pnp/nodejs
pnp - provides functionality enabling the @pnp libraries within nodejs
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pnp/sp | AI (dependencies): Sibling monorepo package from pnp/pnpjs; same version pinned, not an independent risk. | ai | |
| dependencies | unvetted-dep:@pnp/core | AI (dependencies): Sibling monorepo package from pnp/pnpjs; same version pinned. | ai | |
| dependencies | unvetted-dep:@pnp/graph | AI (dependencies): Sibling monorepo package from pnp/pnpjs; same version pinned. | ai | |
| dependencies | unvetted-dep:@pnp/logging | AI (dependencies): Sibling monorepo package from pnp/pnpjs; same version pinned. | ai | |
| dependencies | unvetted-dep:@pnp/queryable | AI (dependencies): Sibling monorepo package from pnp/pnpjs; same version pinned. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for compiled TS packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link dump is typical for PnPjs docs-site pattern; not a spam indicator for this established library. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.20.0 | 7 / 0 | |
| 4.19.0 | 7 / 0 | |
| 4.18.0 | 7 / 0 | |
| 4.17.0 | 7 / 0 | |
| 4.16.0 | 7 / 0 | |
| 4.15.0 | 7 / 0 | |
| 4.14.0 | 7 / 0 | |
| 4.13.0 | 7 / 0 |
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.