← Home

kicad-component-converter

npm
28
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

Keywords

kicadjsonconverterelectronics

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Declared runtime dep used in build/config context; stable false positive for this package. ai
phantom-deps phantom-dep:zustand AI (phantom-deps): Declared runtime dep used in site build; stable false positive for this package. ai
phantom-deps phantom-dep:prettier AI (phantom-deps): Declared runtime dep used for code formatting output; stable false positive. ai
phantom-deps phantom-dep:s-expression AI (phantom-deps): Declared runtime dep for KiCad s-expression parsing; stable false positive. ai
phantom-deps phantom-dep:@tscircuit/math-utils AI (phantom-deps): Declared runtime dep from same ecosystem; stable false positive. ai
phantom-deps phantom-dep:@tscircuit/pcb-viewer AI (phantom-deps): Declared runtime dep used in site build; stable false positive. ai
phantom-deps phantom-dep:circuit-json-to-tscircuit AI (phantom-deps): Declared runtime dep from same tscircuit ecosystem; stable false positive. ai
phantom-deps phantom-dep:@tscircuit/create-snippet-url AI (phantom-deps): Declared runtime dep from same tscircuit ecosystem; stable false positive. ai

Versions (showing 28 of 28)

Version Deps Published
0.1.41 0 / 60
0.1.40 0 / 59
0.1.39 0 / 59
0.1.38 0 / 51
0.1.37 0 / 51
0.1.36 0 / 51
0.1.35 0 / 51
0.1.34 0 / 51
0.1.33 0 / 51
0.1.32 0 / 51
0.1.31 0 / 51
0.1.30 0 / 51
0.1.29 0 / 51
0.1.28 0 / 51
0.1.27 0 / 51
0.1.26 0 / 51
0.1.25 0 / 51
0.1.24 0 / 51
0.1.23 0 / 51
0.1.22 0 / 51
0.1.21 0 / 51
0.1.12 8 / 30
0.1.11 8 / 31
0.1.10 8 / 31
0.1.9 8 / 31
0.1.8 8 / 31
0.1.7 8 / 31
0.1.6 8 / 32

v0.1.41

1 finding
LOW No provenance attestation provenance

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

v0.1.29

1 finding
LOW No provenance attestation provenance

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

v0.1.28

1 finding
LOW No provenance attestation provenance

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

v0.1.27

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

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

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.6

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.