@solidjs/router
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted first-party maintainer; missing gitHead is publish-env metadata, not a threat. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is not a risk for this established package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.16.2 | 0 / 17 | |
| 0.16.1 | 0 / 17 | |
| 0.16.0 | 0 / 17 | |
| 0.15.4 | 0 / 17 | |
| 0.15.3 | 0 / 17 | |
| 0.15.2 | 0 / 17 | |
| 0.15.1 | 0 / 17 | |
| 0.15.0 | 0 / 17 | |
| 0.14.10 | 0 / 17 | |
| 0.14.9 | 0 / 17 | |
| 0.14.8 | 0 / 17 | |
| 0.14.7 | 0 / 17 | |
| 0.14.6 | 0 / 17 | |
| 0.14.5 | 0 / 17 | |
| 0.14.4 | 0 / 17 | |
| 0.14.3 | 0 / 17 | |
| 0.14.2 | 0 / 17 | |
| 0.14.1 | 0 / 17 | |
| 0.14.0 | 0 / 17 | |
| 0.13.6 | 0 / 17 | |
| 0.13.5 | 0 / 17 | |
| 0.13.4 | 0 / 17 | |
| 0.13.3 | 0 / 17 | |
| 0.13.2 | 0 / 17 | |
| 0.13.1 | 0 / 17 | |
| 0.13.0 | 0 / 17 | |
| 0.12.5 | 0 / 17 | |
| 0.12.4 | 0 / 17 | |
| 0.12.3 | 0 / 17 | |
| 0.12.2 | 0 / 17 | |
| 0.12.1 | 0 / 17 | |
| 0.12.0 | 0 / 17 | |
| 0.11.5 | 0 / 17 | |
| 0.11.4 | 0 / 17 | |
| 0.11.3 | 0 / 17 | |
| 0.11.2 | 0 / 17 | |
| 0.11.1 | 0 / 17 | |
| 0.11.0 | 0 / 17 | |
| 0.10.10 | 0 / 16 | |
| 0.10.9 | 0 / 16 | |
| 0.10.8 | 0 / 16 | |
| 0.10.7 | 0 / 16 | |
| 0.10.6 | 0 / 16 | |
| 0.10.5 | 0 / 16 | |
| 0.10.4 | 0 / 16 | |
| 0.10.3 | 0 / 16 | |
| 0.10.2 | 0 / 16 | |
| 0.10.1 | 0 / 16 | |
| 0.10.0 | 0 / 16 | |
| 0.9.1 | 0 / 16 | |
| 0.9.0 | 0 / 16 |
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ryansolid.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.