← Home

cli-table2

npm Repository Homepage

Pretty unicode tables for the command line. Based on the original cli-table.

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

jamestalmage

Keywords

nodecommandlineclitabletablestabularunicodecolorsgrid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): james.talmage and jamestalmage are the same person; this reflects an npm username rename, not a hostile takeover. Stable false positive for this package. ai
provenance publisher-changed AI (provenance): Publisher change from james.talmage to jamestalmage is an npm account rename by the same author (James Talmage). Not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): jamestalmage is the renamed account of the original maintainer james.talmage; addition is benign. ai
maintainer-change maintainer-removed AI (maintainer-change): james.talmage removal is the other side of the account rename; same person, different npm username. ai
publish-pattern new-deps-added AI (publish-pattern): string-width is a well-known Sindre Sorhus utility; natural addition for a CLI table library handling Unicode display widths. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.0 3 / 12
0.1.9 2 / 12
0.1.8 2 / 12
0.1.7 2 / 12
0.1.4 2 / 11
0.1.3 2 / 11
0.1.2 2 / 11
0.1.1 2 / 11
0.1.0 2 / 11
0.0.1 2 / 11

v0.2.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (james.talmage) were replaced by new maintainers (jamestalmage). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: james.talmage → jamestalmage (on 2016-02-03) provenance

This version was published by a different npm account than previous versions on 2016-02-03. 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.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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