← Home

@stackone/malachite

npm

📄 License This project is licensed under the MIT License.

20
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

s1guillaumejorge.stackonestackone-publisher

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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: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
phantom-deps phantom-dep:@uiw/react-json-view AI (phantom-deps): Same as above — bundled component library pattern; heuristic false positive. ai

Versions (showing 20 of 20)

Version Deps Published
0.25.2 2 / 14
0.24.2 2 / 14
0.24.0 2 / 14
0.23.0 2 / 14
0.22.2 2 / 14
0.22.1 2 / 14
0.21.0 2 / 14
0.20.0 2 / 14
0.19.0 2 / 14
0.14.0 2 / 14
0.6.0 2 / 14
0.5.2 2 / 14
0.5.1 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.24.2

1 finding
LOW No provenance attestation provenance

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

v0.24.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.

v0.23.0

1 finding
LOW No provenance attestation provenance

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

v0.22.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.

v0.22.1

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

v0.20.0

1 finding
LOW No provenance attestation provenance

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

v0.19.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.

v0.14.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.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.

v0.5.1

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

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.1

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

v0.1.1

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.