← Home

@pnp/queryable

npm Repository Homepage

pnp - provides shared odata functionality and base classes

23
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrick-rodgerswaldekmvesajuvonenjansenbeofficedevpnpstfbauergarry.trinderappieschotarjunumenoneliostruyf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): PnPjs packages use documentation-heavy READMEs with links; not a spam/phishing indicator for this established Microsoft-affiliated monorepo. ai
dependencies unvetted-dep:@pnp/core AI (dependencies): @pnp/core is a sibling package in the same PnPjs monorepo; always a dependency of @pnp/queryable. ai

Versions (showing 23 of 23)

Version Deps Published
4.20.0 2 / 0
4.19.0 2 / 0
4.18.0 2 / 0
4.17.0 2 / 0
4.16.0 2 / 0
4.15.0 2 / 0
4.14.0 2 / 0
4.13.0 2 / 0
4.12.0 2 / 0
4.11.0 2 / 0
4.10.0 2 / 0
4.9.0 2 / 0
4.8.0 2 / 0
4.7.0 2 / 0
4.6.0 2 / 0
4.5.0 2 / 0
4.4.0 2 / 0
4.3.0 2 / 0
4.2.0 2 / 0
4.1.1 2 / 0
4.1.0 2 / 0
4.0.1 2 / 0
4.0.0 2 / 0

v4.12.0

1 finding
LOW No provenance attestation provenance

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

v4.11.0

1 finding
LOW No provenance attestation provenance

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

v4.10.0

1 finding
LOW No provenance attestation provenance

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

v4.9.0

1 finding
LOW No provenance attestation provenance

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

v4.8.0

1 finding
LOW No provenance attestation provenance

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

v4.7.0

1 finding
LOW No provenance attestation provenance

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

v4.6.0

1 finding
LOW No provenance attestation provenance

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

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.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.0.1

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.0.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.