← Home

ansi-fragments

npm Repository Homepage

A tiny library with builders to help making logs/CLI pretty with a nice DX.

4
Versions
MIT
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

zamotany

Keywords

cliansi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Known publisher with long track record; missing gitHead is a minor provenance signal without other corroborating risk indicators for this package. ai
phantom-deps phantom-dep:del-cli AI (phantom-deps): del-cli is used in the clean script and is a known packaging mistake (should be devDep); not a security concern for this package. ai
provenance no-provenance AI (provenance): Established package with long history and clean publisher record; lack of Sigstore attestation is a best-practice gap, not a security risk for this package. ai

Versions (showing 4 of 4)

Version Deps Published
0.2.1 3 / 9
0.2.0 4 / 8
0.1.1 3 / 9
0.1.0 4 / 5

v0.2.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zamotany.

LOW No provenance attestation provenance

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

v0.2.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zamotany.

INFO No provenance attestation provenance

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

v0.1.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zamotany.

INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.