← Home

@midnight-ntwrk/midnight-js-node-zk-config-provider

npm Repository Homepage
3
Versions
—
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

ntwrk-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:reports/report/assets/index-Dpc7kNBC.js AI (source-diff): Vite-bundled Vue 3 report UI asset; minified but not obfuscated, not part of package runtime exports. ai
provenance no-provenance AI (provenance): Established IOG/midnight-ntwrk org package; lack of provenance is consistent across all versions and not a risk indicator here. ai

Versions (showing 3 of 3)

Version Deps Published
4.1.0 2 / 0
4.0.4 1 / 0
4.0.2 1 / 0

v4.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

2 findings
HIGH New obfuscated file: reports/report/assets/index-Dpc7kNBC.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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