@tinkoff/router
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 | no-provenance | AI (provenance): Large established monorepo package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 51 of 479)
| Version | Deps | Published |
|---|---|---|
| 0.7.129 | 5 / 2 | |
| 0.7.128 | 5 / 2 | |
| 0.7.123 | 5 / 2 | |
| 0.7.122 | 5 / 2 | |
| 0.7.121 | 5 / 2 | |
| 0.7.120 | 5 / 2 | |
| 0.7.119 | 5 / 2 | |
| 0.7.118 | 5 / 2 | |
| 0.7.117 | 5 / 2 | |
| 0.7.116 | 5 / 2 | |
| 0.7.115 | 5 / 2 | |
| 0.7.113 | 5 / 2 | |
| 0.7.112 | 5 / 2 | |
| 0.7.109 | 5 / 2 | |
| 0.7.107 | 5 / 2 | |
| 0.7.106 | 5 / 2 | |
| 0.7.74 | 5 / 2 | |
| 0.7.73 | 5 / 2 | |
| 0.7.71 | 5 / 2 | |
| 0.7.70 | 5 / 2 | |
| 0.7.69 | 5 / 2 | |
| 0.7.67 | 5 / 2 | |
| 0.7.64 | 5 / 2 | |
| 0.7.63 | 5 / 2 | |
| 0.7.62 | 5 / 2 | |
| 0.7.59 | 5 / 2 | |
| 0.7.58 | 5 / 2 | |
| 0.7.56 | 5 / 2 | |
| 0.7.55 | 5 / 2 | |
| 0.7.33 | 5 / 2 | |
| 0.7.32 | 5 / 2 | |
| 0.7.25 | 5 / 2 | |
| 0.7.21 | 5 / 2 | |
| 0.7.19 | 5 / 2 | |
| 0.7.18 | 5 / 2 | |
| 0.7.15 | 5 / 2 | |
| 0.7.14 | 5 / 2 | |
| 0.7.13 | 5 / 2 | |
| 0.7.12 | 5 / 2 | |
| 0.7.11 | 5 / 2 | |
| 0.7.10 | 5 / 2 | |
| 0.7.9 | 5 / 2 | |
| 0.7.8 | 5 / 2 | |
| 0.7.7 | 5 / 2 | |
| 0.7.6 | 5 / 2 | |
| 0.7.5 | 5 / 2 | |
| 0.7.4 | 5 / 2 | |
| 0.7.3 | 5 / 2 | |
| 0.7.2 | 5 / 2 | |
| 0.7.1 | 5 / 2 | |
| 0.6.282 | 5 / 2 |
v0.7.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.