circuit-to-svg No license 51 versions

circuit-to-svg

npm

51

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

seveibar

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@tscircuit/checks	AI (phantom-deps): tscircuit ecosystem dep; referenced in config, stable false positive for this package.	ai	2026/05/09
phantom-deps	phantom-dep:@tscircuit/circuit-json-util	AI (phantom-deps): tscircuit ecosystem dep; referenced in config, stable false positive for this package.	ai	2026/05/09
phantom-deps	phantom-dep:@tscircuit/footprinter	AI (phantom-deps): Part of the tscircuit ecosystem; declared as runtime dep, phantom-dep heuristic is a false positive here.	ai	2026/05/09
phantom-deps	phantom-dep:@tscircuit/routing	AI (phantom-deps): Part of the tscircuit ecosystem; declared as runtime dep, phantom-dep heuristic is a false positive here.	ai	2026/05/09
phantom-deps	phantom-dep:svg-path-commander	AI (phantom-deps): Referenced in config files; stable false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:bun-types	AI (phantom-deps): bun-types is a type package; phantom-dep false positive stable for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a type package loaded by convention; stable false positive.	ai	2026/04/28

Versions (showing 51 of 237)

View all versions

Version	Deps	Published
0.0.353	7 / 18	2026-06-07
0.0.352	7 / 18	2026-06-05
0.0.351	7 / 18	2026-06-04
0.0.350	7 / 18	2026-05-22
0.0.349	7 / 18	2026-05-22
0.0.348	7 / 18	2026-05-21
0.0.347	7 / 18	2026-05-15
0.0.346	7 / 18	2026-05-14
0.0.345	7 / 18	2026-04-22
0.0.344	7 / 18	2026-04-19
0.0.343	7 / 18	2026-04-10
0.0.342	7 / 18	2026-04-09
0.0.341	7 / 18	2026-04-09
0.0.340	7 / 18	2026-03-29
0.0.339	7 / 18	2026-03-25
0.0.338	7 / 18	2026-03-18
0.0.337	7 / 18	2026-03-13
0.0.336	7 / 18	2026-03-12
0.0.335	7 / 18	2026-03-12
0.0.334	7 / 18	2026-03-12
0.0.333	7 / 18	2026-03-02
0.0.332	7 / 18	2026-02-27
0.0.331	7 / 18	2026-02-23
0.0.330	7 / 18	2026-02-20
0.0.329	7 / 18	2026-02-20
0.0.328	7 / 18	2026-02-14
0.0.327	7 / 18	2026-02-06
0.0.326	7 / 18	2026-02-05
0.0.325	7 / 18	2026-02-05
0.0.324	7 / 18	2026-02-04
0.0.323	7 / 18	2026-02-02
0.0.322	7 / 18	2026-02-02
0.0.321	6 / 17	2026-02-01
0.0.320	6 / 17	2026-02-01
0.0.319	6 / 17	2026-01-27
0.0.318	5 / 17	2026-01-27
0.0.317	5 / 17	2026-01-26
0.0.316	5 / 17	2026-01-22
0.0.315	5 / 17	2026-01-17
0.0.314	5 / 17	2026-01-15
0.0.313	5 / 17	2026-01-10
0.0.312	5 / 17	2026-01-09
0.0.311	5 / 17	2026-01-06
0.0.310	5 / 17	2026-01-03
0.0.309	5 / 17	2026-01-03
0.0.308	5 / 17	2026-01-03
0.0.307	5 / 17	2026-01-01
0.0.306	5 / 17	2026-01-01
0.0.305	5 / 17	2025-12-30
0.0.304	5 / 17	2025-12-29
0.0.303	5 / 17	2025-12-26

v0.0.353

1 finding

LOW No provenance attestation provenance

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

v0.0.352

1 finding

LOW No provenance attestation provenance

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

v0.0.351

1 finding

LOW No provenance attestation provenance

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

v0.0.350

1 finding

LOW No provenance attestation provenance

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

v0.0.349

1 finding

LOW No provenance attestation provenance

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

v0.0.348

1 finding

LOW No provenance attestation provenance

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

v0.0.347

1 finding

LOW No provenance attestation provenance

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

v0.0.346

1 finding

LOW No provenance attestation provenance

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

v0.0.345

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.