@stackone/malachite
📄 License This project is licensed under the MIT License.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/CodeBlockHighlighter-CmjV96RB.js | AI (source-diff): Vite bundle output with sourcemap, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-DU-6w0rG.js | AI (source-diff): Vite bundle output with sourcemap, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-virtual | AI (phantom-deps): Used in bundled dist, not visible via source import scan. | ai | |
| source-diff | obfuscated-file:dist/CodeBlockHighlighter-CgZzaCxO.js | AI (source-diff): Vite/esbuild bundled output, not obfuscation; matches new syntax-highlighter feature. | ai | |
| source-diff | obfuscated-file:dist/index-DOugfuM3.js | AI (source-diff): Standard bundled build output for this component library. | ai | |
| phantom-deps | phantom-dep:react-syntax-highlighter | AI (phantom-deps): Used in bundled dist, not visible via source import scan. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): High-cadence automated releases are the norm for this package; rapid publish is expected. | ai | |
| dependencies | unvetted-dep:@uiw/react-json-view | AI (dependencies): @uiw/react-json-view is a known open-source React component; phantom-dep finding indicates it may only be referenced in config, not bundled. | ai | |
| provenance | no-provenance | AI (provenance): Established org publisher with clean track record; absence of Sigstore attestation is not a disqualifier here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package under @stackone org with 34 versions; metadata gaps are cosmetic, not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:@uiw/react-json-view | AI (phantom-deps): Same as above — bundled component library pattern; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:marked-react | AI (phantom-deps): Declared as runtime dep, likely used indirectly via bundled dist; phantom-dep heuristic is unreliable for bundled component libraries. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 0.59.1 | 4 / 18 | |
| 0.59.0 | 4 / 18 | |
| 0.58.1 | 3 / 17 | |
| 0.58.0 | 3 / 17 | |
| 0.57.0 | 3 / 17 | |
| 0.56.0 | 3 / 17 | |
| 0.55.1 | 3 / 17 | |
| 0.55.0 | 3 / 17 | |
| 0.54.1 | 2 / 17 | |
| 0.54.0 | 2 / 17 | |
| 0.53.0 | 2 / 17 | |
| 0.52.2 | 2 / 17 | |
| 0.52.1 | 2 / 17 | |
| 0.52.0 | 2 / 17 | |
| 0.51.0 | 2 / 17 | |
| 0.50.1 | 2 / 17 | |
| 0.50.0 | 2 / 17 | |
| 0.49.0 | 2 / 17 | |
| 0.48.0 | 2 / 17 | |
| 0.47.1 | 2 / 17 | |
| 0.46.0 | 2 / 17 | |
| 0.45.0 | 2 / 17 | |
| 0.44.1 | 2 / 17 | |
| 0.44.0 | 2 / 17 | |
| 0.43.0 | 2 / 17 | |
| 0.42.2 | 2 / 17 | |
| 0.42.1 | 2 / 17 | |
| 0.42.0 | 2 / 17 | |
| 0.41.0 | 2 / 17 | |
| 0.40.0 | 2 / 17 | |
| 0.39.0 | 2 / 17 | |
| 0.38.1 | 2 / 17 | |
| 0.38.0 | 2 / 17 | |
| 0.37.2 | 2 / 15 | |
| 0.37.1 | 2 / 15 | |
| 0.37.0 | 2 / 15 | |
| 0.36.0 | 2 / 15 | |
| 0.35.2 | 2 / 15 | |
| 0.35.1 | 2 / 15 | |
| 0.35.0 | 2 / 15 | |
| 0.34.0 | 2 / 15 | |
| 0.33.3 | 2 / 14 | |
| 0.33.2 | 2 / 14 | |
| 0.33.1 | 2 / 14 | |
| 0.33.0 | 2 / 14 | |
| 0.32.0 | 2 / 14 | |
| 0.31.2 | 2 / 14 | |
| 0.31.1 | 2 / 14 | |
| 0.31.0 | 2 / 14 | |
| 0.30.0 | 2 / 14 | |
| 0.29.1 | 2 / 14 | |
| 0.29.0 | 2 / 14 | |
| 0.28.1 | 2 / 14 | |
| 0.28.0 | 2 / 14 | |
| 0.27.0 | 2 / 14 | |
| 0.26.1 | 2 / 14 | |
| 0.26.0 | 2 / 14 | |
| 0.25.2 | 2 / 14 | |
| 0.24.2 | 2 / 14 | |
| 0.24.1 | 2 / 14 | |
| 0.24.0 | 2 / 14 | |
| 0.23.0 | 2 / 14 | |
| 0.22.2 | 2 / 14 | |
| 0.22.1 | 2 / 14 | |
| 0.22.0 | 2 / 14 | |
| 0.21.0 | 2 / 14 | |
| 0.20.0 | 2 / 14 | |
| 0.19.0 | 2 / 14 | |
| 0.18.0 | 2 / 14 | |
| 0.17.0 | 2 / 14 | |
| 0.16.0 | 2 / 14 | |
| 0.15.0 | 2 / 14 | |
| 0.14.0 | 2 / 14 | |
| 0.13.0 | 2 / 14 | |
| 0.12.0 | 2 / 14 | |
| 0.11.0 | 2 / 14 | |
| 0.10.0 | 2 / 14 | |
| 0.9.0 | 2 / 14 | |
| 0.8.0 | 2 / 14 | |
| 0.7.0 | 2 / 14 | |
| 0.6.0 | 2 / 14 | |
| 0.5.2 | 2 / 14 | |
| 0.5.1 | 2 / 14 | |
| 0.5.0 | 2 / 14 | |
| 0.4.0 | 1 / 14 | |
| 0.3.2 | 1 / 14 | |
| 0.3.1 | 1 / 14 | |
| 0.3.0 | 1 / 14 | |
| 0.2.1 | 1 / 14 | |
| 0.2.0 | 1 / 14 | |
| 0.1.1 | 3 / 21 |
v0.59.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.