← Home

@rxdi/router

npm Repository Homepage

### [Starter application](https://github.com/rxdi/starter-client-lit-html)

100
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

gapirxdi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Publisher has 444 approved packages; this appears to be a routine maintenance release after a long gap, not a takeover. ai
phantom-deps phantom-dep:router-slot AI (phantom-deps): router-slot is a declared runtime dep used via config/build artifacts, not direct import; stable false positive for this package. ai

Versions (showing 100 of 452)

Version Deps Published
0.7.250 1 / 2
0.7.249 1 / 2
0.7.248 1 / 2
0.7.247 1 / 2
0.7.246 1 / 2
0.7.245 1 / 2
0.7.244 1 / 2
0.7.243 1 / 2
0.7.242 1 / 2
0.7.241 1 / 2
0.7.240 1 / 2
0.7.239 1 / 2
0.7.238 1 / 2
0.7.237 1 / 2
0.7.236 1 / 2
0.7.235 1 / 2
0.7.234 1 / 2
0.7.233 1 / 2
0.7.232 1 / 2
0.7.231 1 / 2
0.7.230 1 / 2
0.7.229 1 / 2
0.7.228 1 / 2
0.7.227 1 / 2
0.7.226 1 / 2
0.7.225 1 / 2
0.7.224 1 / 2
0.7.223 1 / 2
0.7.222 1 / 2
0.7.221 1 / 2
0.7.220 1 / 2
0.7.219 1 / 2
0.7.218 1 / 2
0.7.217 1 / 2
0.7.216 1 / 2
0.7.215 1 / 2
0.7.214 1 / 2
0.7.213 1 / 2
0.7.212 1 / 2
0.7.211 1 / 2
0.7.210 1 / 2
0.7.209 1 / 2
0.7.208 1 / 2
0.7.207 1 / 2
0.7.206 1 / 2
0.7.205 1 / 2
0.7.204 1 / 2
0.7.203 1 / 2
0.7.202 1 / 2
0.7.201 1 / 2
0.7.200 1 / 2
0.7.199 1 / 2
0.7.198 1 / 2
0.7.197 1 / 2
0.7.196 1 / 2
0.7.195 1 / 2
0.7.194 1 / 2
0.7.193 1 / 2
0.7.192 1 / 2
0.7.191 1 / 2
0.7.190 1 / 2
0.7.189 1 / 2
0.7.188 1 / 2
0.7.187 1 / 2
0.7.186 1 / 2
0.7.185 1 / 2
0.7.184 1 / 2
0.7.183 1 / 2
0.7.182 1 / 2
0.7.181 1 / 2
0.7.180 1 / 2
0.7.179 1 / 2
0.7.178 1 / 2
0.7.177 1 / 2
0.7.176 1 / 2
0.7.175 1 / 2
0.7.174 1 / 2
0.7.173 1 / 2
0.7.172 1 / 2
0.7.171 1 / 2
0.7.170 1 / 2
0.7.169 1 / 2
0.7.168 1 / 2
0.7.167 1 / 2
0.7.166 1 / 2
0.7.165 1 / 2
0.7.164 1 / 2
0.7.163 1 / 2
0.7.162 1 / 2
0.7.161 1 / 2
0.7.160 1 / 2
0.7.159 1 / 2
0.7.158 1 / 2
0.7.157 1 / 2
0.7.156 1 / 2
0.7.155 1 / 2
0.7.154 1 / 2
0.7.153 1 / 2
0.7.152 1 / 2
0.7.151 1 / 2
Showing 100 of 452 Next page →

v0.7.250

1 finding
LOW No provenance attestation provenance

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

v0.7.180

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.