@midnight-ntwrk/midnight-js-level-private-state-provider
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:reports/report/assets/index-DaKof6xz.js | AI (source-diff): Vite-bundled Vue 3 report UI asset; minified frontend bundle, not malicious obfuscation. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:reports/report/assets/index-Dpc7kNBC.js | AI (source-diff): Minified Vue/Vite bundle inside reports/ directory; not a runtime artifact, just a bundled coverage/test report UI. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established IOG org package; sparse README is a documentation gap, not spam/phishing. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex encoding/decoding used for Buffer serialization in private state provider — legitimate data handling pattern. | ai | |
| phantom-deps | phantom-dep:io-ts | AI (phantom-deps): io-ts referenced in config/type definitions; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used in storage encryption/decryption layer — standard cryptographic utility pattern. | ai | |
| phantom-deps | phantom-dep:fp-ts | AI (phantom-deps): fp-ts referenced in config/type definitions; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 9 / 1 | |
| 4.1.0 | 8 / 0 | |
| 4.0.4 | 7 / 0 | |
| 4.0.2 | 7 / 0 | |
| 4.0.1 | 7 / 0 | |
| 3.2.0 | 7 / 0 | |
| 3.1.0 | 8 / 1 | |
| 3.0.0 | 8 / 1 | |
| 2.1.0 | 8 / 1 |
v4.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.