prettyjson — Greenflagged

Package for formatting JSON data in a coloured YAML-style, perfect for CLI output

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

rafeca

Keywords

jsoncliformattingcolors

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:docs/javascripts/highlight.pack.js	AI (source-diff): This is the well-known highlight.js library bundled as a documentation asset under docs/; it is not runtime code and poses no threat to package consumers.	ai	2026/04/24
source-diff	obfuscated-file:site/javascripts/highlight.pack.js	AI (source-diff): Same highlight.js documentation asset under site/; minification is expected for a browser-side syntax highlighter shipped with static docs.	ai	2026/04/24
source-diff	net-exec-file:site/javascripts/sh_main.min.js	AI (source-diff): This is SHJS, a well-known open-source syntax highlighter in the site/ documentation directory. Not part of runtime package code; the network/exec pattern is benign browser-side DOM manipulation for highlighting.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is 5309 days old and predates Sigstore provenance attestation. No provenance is expected and not a risk signal for this established package.	ai	2026/04/24

Versions (showing 35 of 35)

Version	Deps	Published
1.2.5	2 / 6	2022-01-11
1.2.4	2 / 6	2022-01-10
1.2.3	2 / 6	2022-01-10
1.2.2	2 / 6	2022-01-10
1.2.1	2 / 6	2016-12-01
1.2.0	2 / 6	2016-11-20
1.1.3	2 / 6	2015-08-09
1.1.2	2 / 7	2015-05-21
1.1.1	2 / 7	2015-05-13
1.1.0	2 / 7	2015-02-04
1.0.0	2 / 7	2014-03-21
0.13.0	2 / 7	2014-03-08
0.12.1	1 / 7	2014-03-08
0.12.0	1 / 7	2014-02-11
0.11.1	1 / 7	2014-02-02
0.11.0	1 / 7	2014-02-02
0.10.0	1 / 7	2013-12-10
0.9.0	1 / 7	2013-10-04
0.8.1	1 / 6	2013-03-11
0.8.0	1 / 6	2013-02-23
0.7.1	1 / 6	2012-10-29
0.7.0	1 / 6	2012-10-25
0.6.0	1 / 6	2012-06-29
0.5.0	1 / 6	2012-06-24
0.4.0	1 / 4	2012-02-24
0.3.1	1 / 3	2012-02-15
0.3.0	1 / 3	2012-01-23
0.2.1	1 / 3	2012-01-23
0.2.0	1 / 3	2012-01-22
0.1.4	1 / 1	2011-12-01
0.1.3	1 / 1	2011-11-16
0.1.2	1 / 1	2011-11-13
0.1.1	1 / 1	2011-11-08
0.1.0	1 / 1	2011-10-11
0.0.1	1 / 1	2011-10-10

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

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.

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

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

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

3 findings

HIGH New obfuscated file: docs/javascripts/highlight.pack.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: site/javascripts/highlight.pack.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.5.0

3 findings

HIGH New obfuscated file: docs/javascripts/highlight.pack.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: site/javascripts/highlight.pack.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.0

2 findings

HIGH New file with network + code execution: site/javascripts/sh_main.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.3.1

2 findings

HIGH New file with network + code execution: site/javascripts/sh_main.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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

HIGH New file with network + code execution: site/javascripts/sh_main.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.2.1

2 findings

HIGH New file with network + code execution: site/javascripts/sh_main.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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 New file with network + code execution: site/javascripts/sh_main.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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. Consider requesting the maintainer enable provenance via CI/CD.

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