← Home

babar

npm Repository Homepage

CLI bar charts

7
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

stephan83utix

Keywords

clibarchartsgraphascii

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transfer in 2022; utix has clean track record; no code changes in this version. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition consistent with legitimate transfer; no suspicious code changes. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; common for older packages. ai

Versions (showing 7 of 7)

Version Deps Published
0.2.3 1 / 2
0.2.2 1 / 2
0.2.0 1 / 2
0.1.0 1 / 2
0.0.3 1 / 1
0.0.2 1 / 1
0.0.1 1 / 1

v0.2.3

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

2 findings
HIGH Publisher changed: stephan83 → utix (on 2022-02-17) provenance

This version was published by a different npm account than previous versions on 2022-02-17. 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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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.