← Home

@highflame/yara-x

2
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

akhiljavelinakashjavelinsharathrajasekar

Keywords

yarayara-xmalwaredetectionnapi-rsrust

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Standard napi-rs musl detection pattern; execSync('ldd --version') is boilerplate for selecting prebuilt binary. ai
semgrep semgrep:child-process-execsync AI (semgrep): Standard napi-rs musl detection; fixed command 'ldd --version', no user input involved. ai
semgrep semgrep:dynamic-require AI (semgrep): Standard napi-rs NAPI_RS_NATIVE_LIBRARY_PATH override; documented escape hatch for custom binary paths. ai

Versions (showing 2 of 2)

Version Deps Published
1.0.2 0 / 3
1.0.0 0 / 3

v1.0.2

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.

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