@pnp/graph
pnp - provides a fluent interface to query the Microsoft Graph
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established PnPjs monorepo package; README linking to docs is expected, not a phishing indicator. | ai | |
| dependencies | unvetted-dep:@pnp/core | AI (dependencies): Sibling monorepo package published in lockstep; not an independent unvetted dependency. | ai | |
| dependencies | unvetted-dep:@pnp/queryable | AI (dependencies): Sibling monorepo package published in lockstep; not an independent unvetted dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.20.0 | 4 / 0 | |
| 4.19.0 | 4 / 0 | |
| 4.18.0 | 4 / 0 | |
| 4.17.0 | 4 / 0 | |
| 4.16.0 | 4 / 0 | |
| 4.15.0 | 4 / 0 | |
| 4.14.0 | 4 / 0 | |
| 4.13.0 | 4 / 0 | |
| 4.12.0 | 4 / 0 | |
| 4.11.0 | 4 / 0 | |
| 4.10.0 | 4 / 0 | |
| 4.9.0 | 4 / 0 | |
| 4.8.0 | 4 / 0 | |
| 4.7.0 | 4 / 0 | |
| 4.6.0 | 4 / 0 | |
| 4.5.0 | 4 / 0 | |
| 4.4.0 | 4 / 0 | |
| 4.3.0 | 4 / 0 | |
| 4.2.0 | 4 / 0 | |
| 4.1.1 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 4.0.1 | 4 / 0 | |
| 4.0.0 | 4 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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.