@tscircuit/checks No license 95 versions

@tscircuit/checks

npm

95

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
npm-metadata	url-dep:@tscircuit/jlcpcb-manufacturing-specs	AI (npm-metadata): SHA-pinned dep is in devDependencies only; not shipped to consumers. Stable pattern for this package.	ai	2026/05/14

Versions (showing 95 of 95)

Version	Deps	Published
0.0.137	0 / 13	2026-06-03
0.0.136	0 / 13	2026-06-03
0.0.135	0 / 13	2026-06-03
0.0.134	0 / 13	2026-06-02
0.0.133	0 / 13	2026-05-27
0.0.132	0 / 13	2026-05-22
0.0.131	0 / 13	2026-05-22
0.0.130	0 / 13	2026-05-15
0.0.129	0 / 13	2026-05-13
0.0.128	0 / 13	2026-05-11
0.0.127	0 / 13	2026-05-09
0.0.126	0 / 13	2026-05-06
0.0.125	0 / 13	2026-04-25
0.0.124	0 / 13	2026-04-24
0.0.123	0 / 13	2026-04-24
0.0.122	0 / 13	2026-04-24
0.0.121	0 / 13	2026-04-23
0.0.120	0 / 13	2026-04-21
0.0.119	0 / 12	2026-04-19
0.0.118	0 / 12	2026-04-18
0.0.117	0 / 12	2026-04-16
0.0.116	0 / 12	2026-04-10
0.0.115	0 / 12	2026-03-28
0.0.114	0 / 12	2026-03-18
0.0.113	0 / 12	2026-03-16
0.0.112	0 / 12	2026-03-15
0.0.111	0 / 12	2026-03-13
0.0.110	0 / 12	2026-03-13
0.0.109	0 / 12	2026-03-12
0.0.108	0 / 12	2026-03-12
0.0.107	0 / 12	2026-03-10
0.0.106	0 / 12	2026-03-09
0.0.105	0 / 12	2026-03-08
0.0.104	0 / 12	2026-03-06
0.0.103	0 / 12	2026-03-06
0.0.102	0 / 12	2026-03-05
0.0.101	0 / 12	2026-03-04
0.0.100	0 / 12	2026-03-03
0.0.99	0 / 12	2026-03-02
0.0.98	0 / 12	2026-03-02
0.0.97	0 / 12	2026-03-02
0.0.96	0 / 12	2026-03-02
0.0.95	0 / 13	2026-03-02
0.0.94	0 / 13	2026-03-02
0.0.93	0 / 13	2026-03-02
0.0.92	0 / 13	2026-03-01
0.0.91	0 / 13	2026-02-15
0.0.90	0 / 13	2026-02-14
0.0.89	0 / 13	2026-02-13
0.0.88	0 / 13	2026-02-08
0.0.87	0 / 13	2025-11-23
0.0.86	0 / 13	2025-11-23
0.0.85	0 / 13	2025-10-10
0.0.84	0 / 13	2025-10-06
0.0.83	0 / 13	2025-10-05
0.0.82	0 / 13	2025-10-05
0.0.81	0 / 13	2025-10-05
0.0.80	0 / 13	2025-10-04
0.0.79	0 / 13	2025-10-03
0.0.78	0 / 12	2025-09-27
0.0.77	0 / 12	2025-09-24
0.0.76	0 / 12	2025-09-23
0.0.75	0 / 12	2025-09-11
0.0.74	0 / 12	2025-09-11
0.0.73	0 / 12	2025-09-06
0.0.72	0 / 12	2025-08-19
0.0.71	0 / 12	2025-08-15
0.0.70	0 / 12	2025-08-14
0.0.69	0 / 12	2025-08-12
0.0.68	0 / 12	2025-08-12
0.0.67	0 / 11	2025-08-09
0.0.66	0 / 11	2025-07-31
0.0.65	0 / 11	2025-07-29
0.0.64	0 / 11	2025-07-27
0.0.63	0 / 11	2025-07-27
0.0.62	0 / 11	2025-07-26
0.0.61	0 / 11	2025-07-25
0.0.60	0 / 11	2025-07-23
0.0.59	0 / 11	2025-07-23
0.0.58	0 / 11	2025-07-10
0.0.57	0 / 11	2025-07-10
0.0.56	0 / 11	2025-07-10
0.0.55	0 / 11	2025-07-10
0.0.54	0 / 12	2025-06-29
0.0.53	0 / 12	2025-06-16
0.0.52	0 / 12	2025-06-05
0.0.51	0 / 12	2025-06-01
0.0.50	0 / 12	2025-05-22
0.0.49	0 / 12	2025-05-20
0.0.48	0 / 12	2025-05-16
0.0.47	0 / 12	2025-05-12
0.0.46	3 / 9	2025-05-11
0.0.45	3 / 9	2025-05-10
0.0.44	3 / 9	2025-04-30
0.0.43	3 / 9	2025-04-27

v0.0.137

1 finding

LOW No provenance attestation provenance

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

v0.0.136

1 finding

LOW No provenance attestation provenance

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

v0.0.135

1 finding

LOW No provenance attestation provenance

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

v0.0.134

1 finding

LOW No provenance attestation provenance

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

v0.0.133

1 finding

LOW No provenance attestation provenance

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

v0.0.132

1 finding

LOW No provenance attestation provenance

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

v0.0.131

1 finding

LOW No provenance attestation provenance

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

v0.0.130

1 finding

LOW No provenance attestation provenance

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

v0.0.129

2 findings

HIGH SHA-pinned github dependency (devDependencies): @tscircuit/jlcpcb-manufacturing-specs npm-metadata

Dependency '@tscircuit/jlcpcb-manufacturing-specs' in `devDependencies` points to 'git+https://github.com/tscircuit/jlcpcb-manufacturing-specs.git#e08af159db01a37db007e33f0a7268d0e4a279a5' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.128

2 findings

HIGH SHA-pinned github dependency (devDependencies): @tscircuit/jlcpcb-manufacturing-specs npm-metadata

Dependency '@tscircuit/jlcpcb-manufacturing-specs' in `devDependencies` points to 'git+https://github.com/tscircuit/jlcpcb-manufacturing-specs.git#e08af159db01a37db007e33f0a7268d0e4a279a5' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.127

2 findings

HIGH SHA-pinned github dependency (devDependencies): @tscircuit/jlcpcb-manufacturing-specs npm-metadata

Dependency '@tscircuit/jlcpcb-manufacturing-specs' in `devDependencies` points to 'git+https://github.com/tscircuit/jlcpcb-manufacturing-specs.git#e08af159db01a37db007e33f0a7268d0e4a279a5' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.

LOW No provenance attestation provenance

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

v0.0.126

1 finding

LOW No provenance attestation provenance

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

v0.0.85

1 finding

LOW No provenance attestation provenance

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

v0.0.84

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.0.77

1 finding

LOW No provenance attestation provenance

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

v0.0.76

1 finding

LOW No provenance attestation provenance

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

v0.0.75

1 finding

LOW No provenance attestation provenance

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

v0.0.74

1 finding

LOW No provenance attestation provenance

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

v0.0.73

1 finding

LOW No provenance attestation provenance

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

v0.0.72

1 finding

LOW No provenance attestation provenance

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

v0.0.71

1 finding

LOW No provenance attestation provenance

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

v0.0.70

1 finding

LOW No provenance attestation provenance

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

v0.0.69

1 finding

LOW No provenance attestation provenance

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

v0.0.68

1 finding

LOW No provenance attestation provenance

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

v0.0.67

1 finding

LOW No provenance attestation provenance

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

v0.0.66

1 finding

LOW No provenance attestation provenance

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

v0.0.65

1 finding

LOW No provenance attestation provenance

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

v0.0.64

1 finding

LOW No provenance attestation provenance

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

v0.0.63

1 finding

LOW No provenance attestation provenance

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

v0.0.62

1 finding

LOW No provenance attestation provenance

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

v0.0.61

1 finding

LOW No provenance attestation provenance

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

v0.0.60

1 finding

LOW No provenance attestation provenance

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

v0.0.59

1 finding

LOW No provenance attestation provenance

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

v0.0.58

1 finding

LOW No provenance attestation provenance

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

v0.0.57

1 finding

LOW No provenance attestation provenance

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

v0.0.56

1 finding

LOW No provenance attestation provenance

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

v0.0.55

1 finding

LOW No provenance attestation provenance

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

v0.0.54

1 finding

LOW No provenance attestation provenance

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

v0.0.53

1 finding

LOW No provenance attestation provenance

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

v0.0.52

1 finding

LOW No provenance attestation provenance

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

v0.0.51

1 finding

LOW No provenance attestation provenance

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

v0.0.50

1 finding

LOW No provenance attestation provenance

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

v0.0.49

1 finding

LOW No provenance attestation provenance

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

v0.0.48

1 finding

LOW No provenance attestation provenance

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

v0.0.47

1 finding

LOW No provenance attestation provenance

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

v0.0.46

1 finding

LOW No provenance attestation provenance

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

v0.0.45

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

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

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.