← Home

@unrs/resolver-binding-linux-riscv64-gnu

UnRS Resolver Node API

34
Versions
MIT
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

jounqin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific native binding package; .node binary is the intended artifact, backed by SLSA provenance. ai
bogus-package bogus-package AI (bogus-package): Platform shard packages legitimately have no deps, no keywords, and minimal READMEs by design. ai

Versions (showing 34 of 34)

Version Deps Published
1.12.2 0 / 0
1.12.1 0 / 0
1.12.0 0 / 0
1.11.1 0 / 0
1.11.0 0 / 0
1.10.1 0 / 0
1.10.0 0 / 0
1.9.2 0 / 0
1.9.1 0 / 0
1.9.0 0 / 0
1.8.1 0 / 0
1.8.0 0 / 0
1.7.13 0 / 0
1.7.12 0 / 0
1.7.11 0 / 0
1.7.10 0 / 0
1.7.9 0 / 0
1.7.8 0 / 0
1.7.7 0 / 0
1.7.6 0 / 0
1.7.5 0 / 0
1.7.4 0 / 0
1.7.3 0 / 0
1.7.2 0 / 0
1.7.1 0 / 0
1.7.0 0 / 0
1.6.6 0 / 0
1.6.5 0 / 0
1.6.4 0 / 0
1.6.3 0 / 0
1.6.2 0 / 0
1.6.1 0 / 0
1.6.0 0 / 0
1.5.0 0 / 0

v1.7.2

1 finding
LOW No provenance attestation provenance

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

v1.7.1

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.6

1 finding
LOW No provenance attestation provenance

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

v1.6.5

1 finding
LOW No provenance attestation provenance

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

v1.6.4

1 finding
LOW No provenance attestation provenance

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

v1.6.3

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.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.