← Home

@ruvector/gnn

npm Repository Homepage
9
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ruvnet

Keywords

ruvectorgnngraph-neural-networkmachine-learningvector-databasehnswnapi-rs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:got AI (typosquat): Scoped napi-rs GNN binding; no relation to the 'got' HTTP library. Levenshtein match is coincidental. ai
semgrep semgrep:child-process-import AI (semgrep): Used solely for 'which ldd' musl detection in napi-rs binary loader; stable pattern for this package. ai
semgrep semgrep:child-process-execsync AI (semgrep): execSync('which ldd') is the standard napi-rs musl detection idiom; not arbitrary command execution. ai

Versions (showing 9 of 9)

Version Deps Published
0.1.25 0 / 1
0.1.24 0 / 1
0.1.23 0 / 1
0.1.22 0 / 1
0.1.21 0 / 1
0.1.19 0 / 1
0.1.18 0 / 1
0.1.17 0 / 1
0.1.15 0 / 1

v0.1.24

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.

v0.1.23

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.

v0.1.22

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.

v0.1.21

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.

v0.1.19

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.

v0.1.18

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.

v0.1.17

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.

v0.1.15

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.