← Home

ansi-colors

npm Repository Homepage

Easily add ANSI colors to your text and symbols in the terminal. A faster drop-in replacement for chalk, kleur and turbocolor (without the dependencies and rendering bugs).

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

jonschlinkertdoowb

Keywords

256ansibgblackbgBlackbgbluebgBluebgcyanbgCyanbggreenbgGreenbgmagentabgMagentabgredbgRedbgwhitebgWhitebgyellowbgYellowblackblueboldclicloroxcolorcolorscolourcommand linecommand-lineconsolecyandimformattinggraygreengreyhiddeninverseitalickleurlogloggingmagentaredresetrgbshellstrstrikethroughstringstylestylesterminaltextttyunderlinewhitextermyellow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): doowb is the package author/repo owner and known collaborator of jonschlinkert; legitimate maintainer with strong track record. ai

Versions (showing 29 of 29)

Version Deps Published
4.1.3 0 / 5
4.1.2 0 / 5
4.1.1 0 / 5
4.1.0 0 / 5
4.0.1 0 / 5
3.2.4 0 / 5
3.2.3 0 / 5
3.2.2 0 / 5
3.2.1 0 / 5
3.2.0 0 / 5
3.1.0 0 / 5
3.0.6 0 / 4
3.0.5 0 / 4
3.0.4 0 / 4
3.0.3 0 / 4
3.0.2 0 / 4
3.0.1 0 / 4
3.0.0 0 / 4
2.0.5 0 / 4
2.0.4 0 / 4
2.0.3 0 / 4
2.0.2 0 / 4
2.0.1 0 / 4
2.0.0 0 / 4
1.1.0 1 / 3
1.0.1 1 / 2
1.0.0 1 / 2
0.2.0 27 / 2
0.1.0 27 / 1

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v3.2.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2019-03-03) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-03. This could indicate a legitimate maintainer transition or an account compromise.

v3.2.3

1 finding
LOW No provenance attestation provenance

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

v3.2.2

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2018-12-04) provenance

This version was published by a different npm account than previous versions on 2018-12-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2018-08-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-19. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.1

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2018-08-18) provenance

This version was published by a different npm account than previous versions on 2018-08-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2018-08-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-16. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

1 finding
LOW No provenance attestation provenance

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