loggy MIT 19 versions

loggy

npm Repository Homepage

Dead-simple colored logger for stdout.

19

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

paulmillrshvaikalesh

Keywords

logloggertastysimple

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): The new dep (turbocolor) is a legitimate chalk replacement; the swap is a straightforward dependency update with no malicious indicators.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher changed to paulmillr, who is the original author listed in package.json and owns the GitHub repo. Legitimate ownership reclaim, not a compromise.	ai	2026/04/24

Versions (showing 19 of 19)

Version	Deps	Published
1.0.8	2 / 2	2019-09-26
1.0.7	2 / 2	2019-09-26
1.0.6	2 / 2	2019-09-26
1.0.5	2 / 2	2019-09-26
1.0.4	2 / 2	2018-09-14
1.0.3	2 / 2	2018-07-14
1.0.2	2 / 2	2017-02-15
1.0.1	2 / 2	2017-01-27
1.0.0	1 / 2	2017-01-26
0.3.5	2 / 1	2016-05-30
0.3.4	2 / 1	2016-05-30
0.3.3	2 / 1	2016-04-25
0.3.2	2 / 1	2016-04-02
0.3.1	2 / 1	2016-02-24
0.3.0	2 / 0	2016-02-19
0.2.2	3 / 0	2015-08-06
0.2.1	3 / 0	2015-08-05
0.2.0	3 / 0	2013-05-12
0.1.0	3 / 0	2013-02-27

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

2 findings

HIGH Publisher changed: shvaikalesh → paulmillr (on 2019-09-26) provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

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: paulmillr → shvaikalesh (on 2018-07-14) provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.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.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

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

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