← Home

log-utils

npm Repository Homepage

Tiny wrapper around ansi-colors to add colored symbols and a timestamp.

10
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

doowbjonschlinkert

Keywords

ansichalkcheckcheckmarkclicolorcolorscommandconsolecyanerrorgreeninfolinelogredstampsuccessterminaltimetime-stamptimestamputilutilityutilswarnwarningyellow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonschlinkert is the listed author in package.json and repo owner; the transfer from doowb to jonschlinkert is a documented legitimate handoff for this package. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.0 2 / 2
0.3.0 7 / 3
0.2.1 7 / 4
0.2.0 7 / 4
0.1.5 7 / 4
0.1.4 6 / 2
0.1.3 6 / 2
0.1.2 6 / 2
0.1.1 6 / 2
0.1.0 6 / 2

v1.0.0

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

This version was published by a different npm account than previous versions on 2018-11-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.

v0.3.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: jonschlinkert → doowb (on 2018-08-01) provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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