← Home

@unrs/resolver-binding-openharmony-arm64

npm Repository Homepage

UnRS Resolver Node API

4
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 is a placeholder stub for a native binding target platform; consistent with the publisher's other binding packages. ai
npm-metadata no-description AI (npm-metadata): Native binding stub; missing description is consistent with the package's role. ai
npm-metadata bundled-binaries AI (npm-metadata): Platform-specific NAPI binary shard; .node file is the sole deliverable, published with SLSA provenance. ai
bogus-package bogus-package AI (bogus-package): Binary-only platform shard packages legitimately have no deps, no code examples, and no keywords. ai

Versions (showing 4 of 4)

Version Deps Published
1.12.2 0 / 0
1.12.1 0 / 0
1.12.0 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.openharmony-arm64.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.

v1.12.1

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

Package contains compiled binaries that could be backdoors: • resolver.openharmony-arm64.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.

v1.12.0

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

Package contains compiled binaries that could be backdoors: • resolver.openharmony-arm64.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.