← Home

@tscircuit/capacity-autorouter

npm
100
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.

SourceRuleReasonAccepted byWhen
npm-metadata url-dep:dataset-srj18 AI (npm-metadata): devDependency only; tscircuit org repo matching publisher identity; same pattern as other accepted URL deps in this package. ai
npm-metadata url-dep:@tscircuit/autorouting-dataset-01 AI (npm-metadata): devDependency only; tscircuit org repo matching publisher identity; same pattern as other accepted URL deps in this package. ai
npm-metadata url-dep:@tsci/tscircuit.dataset-srj16-bga-breakouts AI (npm-metadata): devDependency SHA-pinned to tscircuit org's own repo; same pattern as all other accepted url-deps in this package. ai
npm-metadata url-dep:high-density-repair01 AI (npm-metadata): devDependency test fixture from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:high-density-repair03 AI (npm-metadata): devDependency test fixture from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:dataset-srj11-45-degree AI (npm-metadata): devDependency test dataset from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:@tscircuit/dataset-srj05 AI (npm-metadata): devDependency test dataset from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:high-density-dataset-z04 AI (npm-metadata): devDependency test dataset from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:@tsci/tscircuit.dataset-srj12-bus-routing AI (npm-metadata): devDependency test dataset from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:@tscircuit/rectdiff AI (npm-metadata): devDependency from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:pcb-poly-hyper-graph AI (npm-metadata): devDependency from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:tiny-hypergraph-poly AI (npm-metadata): devDependency from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:high-density-repair02 AI (npm-metadata): devDependency from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:@tscircuit/fixed-via-hypergraph-solver AI (npm-metadata): devDependency from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:@tsci/seveibar.dataset-srj13 AI (npm-metadata): devDependency test dataset from tscircuit org; not shipped to consumers. ai
npm-metadata url-dep:zdwiel-dataset AI (npm-metadata): devDependency benchmark dataset pinned by SHA; not shipped to consumers. ai
npm-metadata url-dep:tiny-hypergraph AI (npm-metadata): devDependency test fixture from tscircuit org; not shipped to consumers. ai
phantom-deps phantom-dep:bun-match-svg AI (phantom-deps): Likely used in test/build scripts referenced via config rather than direct import; stable FP. ai
phantom-deps phantom-dep:fast-json-stable-stringify AI (phantom-deps): Listed as a runtime dep in package.json; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:object-hash AI (phantom-deps): Listed as a runtime dep in package.json; phantom-dep heuristic false positive for this package. ai

Versions (showing 100 of 409)

Version Deps Published
0.0.164 3 / 38
0.0.163 3 / 38
0.0.162 3 / 38
0.0.161 3 / 38
0.0.160 3 / 38
0.0.159 3 / 38
0.0.158 3 / 38
0.0.157 3 / 37
0.0.156 3 / 37
0.0.155 3 / 37
0.0.154 3 / 37
0.0.153 3 / 37
0.0.152 3 / 37
0.0.151 3 / 37
0.0.150 3 / 37
0.0.149 3 / 37
0.0.148 3 / 37
0.0.147 3 / 37
0.0.146 3 / 37
0.0.145 2 / 37
0.0.144 2 / 37
0.0.143 2 / 37
0.0.142 2 / 37
0.0.141 2 / 37
0.0.140 2 / 37
0.0.139 2 / 37
0.0.138 2 / 37
0.0.137 2 / 37
0.0.136 2 / 37
0.0.135 2 / 37
0.0.134 2 / 37
0.0.133 2 / 37
0.0.132 2 / 37
0.0.131 2 / 37
0.0.130 2 / 37
0.0.129 2 / 37
0.0.128 2 / 37
0.0.127 2 / 35
0.0.126 2 / 35
0.0.125 2 / 35
0.0.124 2 / 35
0.0.123 2 / 35
0.0.122 2 / 35
0.0.121 2 / 35
0.0.120 2 / 35
0.0.119 2 / 35
0.0.118 2 / 35
0.0.117 2 / 35
0.0.116 2 / 35
0.0.115 2 / 35
0.0.114 2 / 35
0.0.113 2 / 35
0.0.112 2 / 35
0.0.111 2 / 35
0.0.110 2 / 35
0.0.109 2 / 35
0.0.108 2 / 35
0.0.107 2 / 35
0.0.106 2 / 34
0.0.105 2 / 34
0.0.104 2 / 34
0.0.103 2 / 34
0.0.102 2 / 34
0.0.101 2 / 34
0.0.100 2 / 34
0.0.99 2 / 34
0.0.98 2 / 34
0.0.97 2 / 34
0.0.96 2 / 34
0.0.95 2 / 34
0.0.94 2 / 34
0.0.93 2 / 34
0.0.92 2 / 34
0.0.91 2 / 34
0.0.90 2 / 34
0.0.89 2 / 34
0.0.88 2 / 34
0.0.87 2 / 34
0.0.86 2 / 34
0.0.85 2 / 34
0.0.84 2 / 34
0.0.83 2 / 34
0.0.82 2 / 34
0.0.81 2 / 34
0.0.80 2 / 34
0.0.79 2 / 34
0.0.78 2 / 34
0.0.77 2 / 34
0.0.76 2 / 34
0.0.75 2 / 34
0.0.74 2 / 34
0.0.73 2 / 34
0.0.72 2 / 34
0.0.71 2 / 34
0.0.70 2 / 34
0.0.69 2 / 34
0.0.68 2 / 34
0.0.67 2 / 34
0.0.66 2 / 34
0.0.65 2 / 34
Showing 100 of 409 Next page →

v0.0.136

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.