← Home

@unrs/resolver-binding-linux-loong64-musl

npm Repository Homepage

UnRS Resolver Node API

2
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jounqin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 versioning used across unrs-resolver's platform binding packages. ai
npm-metadata bundled-binaries AI (npm-metadata): Expected native binary for platform-specific resolver binding package. ai
bogus-package bogus-package AI (bogus-package): Minimal README/deps is normal for auto-generated binary sub-packages. ai

Versions (showing 2 of 2)

Version Deps Published
1.12.2 0 / 0
0.0.0 0 / 0

v1.12.2

2 findings
HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • resolver.linux-loong64-musl.node

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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