@tsonic/cli No license 32 versions

@tsonic/cli

npm

Command-line interface for Tsonic compiler

32

Versions

—

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

jeswin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): DLLs are the .NET compiler runtime for the tsonic CLI; expected for this package type.	ai	2026/05/19
typosquat	typosquat.levenshtein:joi	AI (typosquat): @tsonic/cli is a scoped compiler CLI; Levenshtein match to 'joi' is coincidental and not a typosquat.	ai	2026/04/30
phantom-deps	phantom-dep:@tsonic/tsbindgen	AI (phantom-deps): Same org scope; likely used transitively or via CLI invocation rather than direct import.	ai	2026/04/30

Versions (showing 32 of 32)

Version	Deps	Published
0.0.83	4 / 5	2026-05-31
0.0.82	4 / 5	2026-05-23
0.0.81	4 / 5	2026-05-20
0.0.80	4 / 5	2026-05-20
0.0.79	4 / 5	2026-05-20
0.0.78	4 / 5	2026-05-17
0.0.77	4 / 5	2026-05-16
0.0.76	4 / 5	2026-04-27
0.0.75	4 / 5	2026-04-27
0.0.24	4 / 5	2026-01-14
0.0.23	4 / 5	2026-01-13
0.0.22	4 / 5	2026-01-12
0.0.21	4 / 5	2026-01-12
0.0.20	4 / 5	2026-01-12
0.0.19	3 / 5	2026-01-12
0.0.18	3 / 5	2026-01-12
0.0.17	3 / 5	2026-01-12
0.0.16	3 / 5	2026-01-11
0.0.15	3 / 5	2026-01-09
0.0.14	3 / 5	2025-12-27
0.0.13	3 / 5	2025-12-26
0.0.12	3 / 5	2025-12-09
0.0.10	3 / 5	2025-12-07
0.0.9	3 / 5	2025-12-07
0.0.8	3 / 5	2025-12-03
0.0.7	3 / 5	2025-12-03
0.0.6	3 / 5	2025-12-02
0.0.5	3 / 5	2025-12-02
0.0.4	3 / 5	2025-11-28
0.0.3	3 / 5	2025-11-28
0.0.2	3 / 5	2025-11-28
0.0.1	3 / 5	2025-11-28

v0.0.83

1 finding

LOW No provenance attestation provenance

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

v0.0.82

1 finding

LOW No provenance attestation provenance

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

v0.0.81

1 finding

LOW No provenance attestation provenance

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

v0.0.80

1 finding

LOW No provenance attestation provenance

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

v0.0.79

1 finding

LOW No provenance attestation provenance

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

v0.0.78

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.77

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.76

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.75

2 findings

HIGH Bundled binary files (1) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.Runtime.dll

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

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.23

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.22

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.21

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.20

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.19

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.18

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.17

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.16

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.15

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.14

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.13

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.12

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.10

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.9

2 findings

HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/nodejs.dll • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.8

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.7

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.6

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.5

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.4

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

v0.0.3

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • runtime/Tsonic.JSRuntime.dll • runtime/Tsonic.Runtime.dll

LOW No provenance attestation provenance

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

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.

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.