@tokscale/cli MIT 37 versions

@tokscale/cli

npm Repository

A high-performance CLI tool and visualization dashboard for tracking AI coding assistant token usage and costs across multiple platforms.

37

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

junhoyeo

Keywords

tokscaleopencodeclaude-codecursorgeminicodexcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:date-fns	AI (phantom-deps): date-fns is explicitly declared in package.json; phantom-dep heuristic misfires for this package.	ai	2026/05/31
phantom-deps	phantom-dep:react	AI (phantom-deps): react is a declared runtime dep used by @opentui/react TUI framework; not a true phantom dep for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@opentui/core	AI (phantom-deps): UI framework dep referenced in config/build context; not a real phantom dep for this CLI package.	ai	2026/05/18
phantom-deps	phantom-dep:@opentui/react	AI (phantom-deps): UI framework dep referenced in config/build context; not a real phantom dep for this CLI package.	ai	2026/05/18
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @tokscale/cli is unrelated to joi; Levenshtein match is coincidental.	ai	2026/05/06

Versions (showing 37 of 37)

Version	Deps	Published
3.0.0	0 / 2	2026-05-28
2.1.3	0 / 2	2026-05-18
2.1.2	0 / 2	2026-05-18
2.1.1	0 / 2	2026-05-10
2.1.0	0 / 2	2026-05-01
2.0.27	0 / 2	2026-04-21
2.0.26	0 / 2	2026-04-20
2.0.25	0 / 2	2026-04-17
2.0.24	0 / 2	2026-04-15
2.0.23	0 / 2	2026-04-15
2.0.22	0 / 2	2026-04-12
2.0.21	0 / 2	2026-04-10
2.0.20	0 / 2	2026-04-07
2.0.19	0 / 2	2026-04-06
2.0.18	0 / 2	2026-04-05
2.0.17	0 / 2	2026-04-01
2.0.16	0 / 2	2026-03-31
2.0.15	0 / 2	2026-03-29
2.0.14	0 / 2	2026-03-25
2.0.13	0 / 2	2026-03-17
2.0.12	0 / 2	2026-03-15
2.0.11	0 / 2	2026-03-13
2.0.10	0 / 2	2026-03-11
2.0.9	0 / 2	2026-03-07
2.0.8	0 / 2	2026-03-06
2.0.7	0 / 2	2026-03-05
2.0.6	0 / 2	2026-03-05
2.0.5	0 / 2	2026-03-04
2.0.4	0 / 2	2026-03-02
2.0.3	0 / 2	2026-03-02
2.0.2	0 / 2	2026-02-26
2.0.1	0 / 2	2026-02-26
2.0.0	0 / 2	2026-02-26
1.2.4	13 / 2	2026-02-15
1.0.14	15 / 3	2025-12-24
1.0.2	13 / 4	2025-12-19
1.0.0	13 / 4	2025-12-18

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

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

v2.0.27

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.

v2.0.26

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.

v2.0.25

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.

v2.0.24

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.

v2.0.23

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.

v2.0.22

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.

v2.0.21

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.

v2.0.20

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.

v2.0.19

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.

v2.0.18

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.

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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

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

v1.0.14

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.

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

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