table — Greenflagged

Formats data into a string table.

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

gajusgajus-table

Keywords

asciitexttablealignansi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tv4	AI (phantom-deps): Phantom dependency pattern is stable for this package; tv4 is used indirectly in build/config processing.	ai	2026/04/23
phantom-deps	phantom-dep:string-width	AI (phantom-deps): Phantom dependency pattern is stable for this package; string-width is used indirectly in build/config processing.	ai	2026/04/23
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Phantom dependency pattern is stable for this package; lodash is used indirectly in build/config processing.	ai	2026/04/23
phantom-deps	phantom-dep:ansi-slice	AI (phantom-deps): Phantom dependency pattern is stable for this package; ansi-slice is used indirectly in build/config processing.	ai	2026/04/23
phantom-deps	phantom-dep:chalk	AI (phantom-deps): chalk is declared as a runtime dependency and used in the compiled dist output; static analysis misses it due to the transpiled build. Legitimate for this package.	ai	2026/04/22
dependencies	unvetted-dep:ansi-slice	AI (dependencies): ansi-slice is a small, legitimate ANSI string slicing utility appropriate for a table formatter; no malicious indicators found.	ai	2026/04/22
provenance	no-provenance	AI (provenance): Package predates npm provenance attestation by many years; absence is expected and not a security signal for this package.	ai	2026/04/22
phantom-deps	phantom-dep:strip-ansi	AI (phantom-deps): Phantom dep detection doesn't trace through Babel-compiled dist output; false positive for this transpiled package.	ai	2026/04/22
npm-metadata	url-dep:xregexp	AI (npm-metadata): xregexp is pinned to a specific immutable commit hash, making it stable. This is a legitimate practice for packages not on npm at the time; not a security risk for this package.	ai	2026/04/22
phantom-deps	phantom-dep:xregexp	AI (phantom-deps): Phantom dep detection doesn't trace through Babel-compiled dist output; false positive for this transpiled package.	ai	2026/04/22
phantom-deps	phantom-dep:bluebird	AI (phantom-deps): Phantom dep detection doesn't trace through Babel-compiled dist output; false positive for this transpiled package.	ai	2026/04/22
phantom-deps	phantom-dep:string-length	AI (phantom-deps): Phantom dep detection doesn't trace through Babel-compiled dist output; false positive for this transpiled package.	ai	2026/04/22
source-diff	large-new-source-files	AI (source-diff): New files are compiled TypeScript output and AJV-generated validators, fully explained by the transparent build pipeline in package.json scripts.	ai	2026/04/22
publish-pattern	new-deps-added	AI (publish-pattern): strip-ansi is a well-known, reputable sindresorhus package; natural dependency for an ANSI-aware table formatter.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): gajus-table is the same maintainer's dedicated npm account; consistent with the publisher-changed finding and no hostile takeover indicators.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): The gajus→gajus-table transition is a documented, legitimate account change for this package. Author metadata and repo URL remain consistent with original maintainer.	ai	2026/04/22
dependencies	unvetted-dep:lodash.truncate	AI (dependencies): lodash.truncate is a well-known, widely-used lodash sub-package with a long track record; not a real risk for this package.	ai	2026/04/21

Versions (showing 87 of 87)

Version	Deps	Published
6.9.0	5 / 25	2024-12-03
6.8.2	5 / 25	2024-03-26
6.8.1	5 / 25	2022-11-02
6.8.0	5 / 25	2022-01-05
6.7.6	5 / 25	2022-01-05
6.7.5	5 / 25	2021-12-01
6.7.4	5 / 25	2021-12-01
6.7.3	5 / 25	2021-11-04
6.7.2	6 / 26	2021-09-30
6.7.1	6 / 26	2021-05-14
6.7.0	6 / 26	2021-05-07
6.6.0	7 / 27	2021-04-27
6.5.1	7 / 27	2021-04-23
6.5.0	7 / 27	2021-04-23
6.4.0	6 / 27	2021-04-23
6.3.4	6 / 27	2021-04-23
6.3.3	6 / 27	2021-04-22
6.3.2	9 / 29	2021-04-20
6.3.1	9 / 28	2021-04-20
6.3.0	9 / 28	2021-04-19
6.2.0	9 / 26	2021-04-19
6.1.0	9 / 26	2021-04-14
6.0.9	9 / 26	2021-03-30
6.0.8	9 / 27	2021-03-29
6.0.7	4 / 25	2021-01-04
6.0.6	4 / 25	2021-01-02
6.0.5	4 / 25	2021-01-02
6.0.4	4 / 24	2020-11-19
6.0.3	4 / 24	2020-09-04
6.0.2	3 / 23	2020-09-03
6.0.1	4 / 24	2020-08-30
6.0.0	4 / 24	2020-08-30
5.4.6	4 / 24	2019-08-15
5.4.5	4 / 24	2019-07-31
5.4.4	4 / 23	2019-07-16
5.4.3	4 / 23	2019-07-16
5.4.2	4 / 23	2019-07-16
5.4.1	4 / 23	2019-06-16
5.4.0	4 / 23	2019-05-23
5.3.3	4 / 23	2019-05-11
5.3.2	4 / 23	2019-05-09
5.3.1	4 / 23	2019-05-09
5.3.0	4 / 23	2019-05-09
5.2.3	4 / 23	2019-02-10
5.2.2	4 / 23	2019-01-27
5.2.1	4 / 23	2019-01-14
5.2.0	4 / 23	2019-01-11
5.1.1	4 / 23	2018-11-29
5.1.0	4 / 23	2018-09-30
5.0.2	4 / 23	2018-09-04
5.0.1	5 / 23	2018-09-04
5.0.0	4 / 23	2018-09-04
4.0.3	6 / 15	2018-02-24
4.0.2	6 / 15	2017-09-26
4.0.1	6 / 15	2016-11-22
3.8.3	6 / 16	2016-10-18
3.8.2	6 / 16	2016-10-18
3.8.0	6 / 11	2016-09-17
3.7.10	6 / 11	2016-09-17
3.7.9	5 / 5	2016-09-16
3.7.8	8 / 5	2016-01-19
3.7.7	8 / 5	2016-01-19
3.7.6	8 / 5	2016-01-19
3.7.5	8 / 5	2016-01-19
3.7.4	8 / 4	2015-11-19
3.7.3	8 / 4	2015-10-26
3.7.1	8 / 15	2015-10-26
3.7.0	8 / 15	2015-10-19
3.6.2	8 / 15	2015-10-09
3.6.1	8 / 15	2015-10-08
3.6.0	8 / 15	2015-10-08
3.5.0	9 / 14	2015-10-04
3.4.0	8 / 14	2015-10-04
3.3.0	8 / 14	2015-10-04
3.2.0	8 / 14	2015-10-04
3.1.0	8 / 14	2015-10-04
3.0.1	8 / 14	2015-10-04
2.1.2	9 / 13	2015-09-17
2.1.1	8 / 14	2015-09-17
2.1.0	8 / 13	2015-09-15
2.0.1	8 / 13	2015-09-14
2.0.0	8 / 13	2015-09-14
1.0.0	7 / 13	2015-09-14
0.0.5	1 / 0	2011-02-06
0.0.4	1 / 0	2011-01-18
0.0.3	1 / 0	2011-01-09
0.0.2	0 / 0	2011-01-03

v6.8.2

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2024-03-26) provenance

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

v6.8.1

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2022-11-02) provenance

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

v6.8.0

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2022-01-05) provenance

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

v6.7.6

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2022-01-05) provenance

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

v6.7.5

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2021-12-01) provenance

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

v6.7.4

2 findings

HIGH Publisher changed: gajus → gajus-table (on 2021-12-01) provenance

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

v6.7.3

1 finding

LOW No provenance attestation provenance

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

v6.7.2

1 finding

LOW No provenance attestation provenance

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

v6.7.1

1 finding

LOW No provenance attestation provenance

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

v6.7.0

1 finding

LOW No provenance attestation provenance

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

v6.6.0

1 finding

LOW No provenance attestation provenance

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

v6.5.1

1 finding

LOW No provenance attestation provenance

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

v6.5.0

1 finding

LOW No provenance attestation provenance

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

v6.4.0

1 finding

LOW No provenance attestation provenance

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

v6.3.4

1 finding

LOW No provenance attestation provenance

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

v6.3.3

1 finding

LOW No provenance attestation provenance

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

v6.3.2

1 finding

LOW No provenance attestation provenance

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

v6.3.1

1 finding

LOW No provenance attestation provenance

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

v6.3.0

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.9

1 finding

LOW No provenance attestation provenance

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

v6.0.8

1 finding

LOW No provenance attestation provenance

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

v6.0.7

1 finding

LOW No provenance attestation provenance

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

v6.0.6

1 finding

LOW No provenance attestation provenance

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

v6.0.5

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.

v6.0.4

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.

v6.0.3

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.

v6.0.2

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.

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

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

v5.4.6

1 finding

LOW No provenance attestation provenance

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

v5.4.5

1 finding

LOW No provenance attestation provenance

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

v5.4.4

1 finding

LOW No provenance attestation provenance

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

v5.4.3

1 finding

LOW No provenance attestation provenance

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

v5.4.2

1 finding

LOW No provenance attestation provenance

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

v5.4.1

1 finding

LOW No provenance attestation provenance

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

v5.4.0

1 finding

LOW No provenance attestation provenance

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

v5.3.3

1 finding

LOW No provenance attestation provenance

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

v5.3.2

1 finding

LOW No provenance attestation provenance

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

v5.3.1

1 finding

LOW No provenance attestation provenance

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

v5.3.0

1 finding

LOW No provenance attestation provenance

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

v5.2.3

1 finding

LOW No provenance attestation provenance

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

v5.2.2

1 finding

LOW No provenance attestation provenance

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

v5.2.1

1 finding

LOW No provenance attestation provenance

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

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.1.0

1 finding

LOW No provenance attestation provenance

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

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.0.3

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.

v4.0.2

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.

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

v3.8.3

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.

v3.8.2

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.

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

v3.7.10

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.

v3.7.9

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.

v3.7.8

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.

v3.7.7

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.

v3.7.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.6.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.6.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.6.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.5.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.4.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

v3.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

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.

v0.0.4

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.

v0.0.3

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.

v0.0.2

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.