← Home

@effectstream/npm-midnight-node

npm Repository Homepage

Downloads and starts the binary for Midnight Node

4
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

edwarddc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): Package's documented purpose is to spawn a binary node process; child_process use is expected and benign. ai
phantom-deps phantom-dep:axios-proxy-builder AI (phantom-deps): Declared as a runtime dependency; likely used indirectly via axios configuration rather than direct import. ai

Versions (showing 4 of 4)

Version Deps Published
0.100.10 3 / 0
0.100.9 3 / 0
0.100.8 3 / 0
0.3.99 3 / 0

v0.100.10

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

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

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

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.