@tramvai/tools-check-versions
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tinkoff/logger | AI (dependencies): First-party Tinkoff logger used throughout the tramvai ecosystem; stable false positive for this package. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 6 / 2 | |
| 0.9.2 | 6 / 2 | |
| 0.9.1 | 6 / 2 | |
| 0.8.5 | 6 / 2 | |
| 0.8.4 | 6 / 2 | |
| 0.8.3 | 6 / 2 | |
| 0.8.2 | 6 / 2 | |
| 0.8.1 | 6 / 2 | |
| 0.8.0 | 6 / 2 | |
| 0.7.13 | 6 / 2 | |
| 0.7.12 | 6 / 2 | |
| 0.7.11 | 6 / 2 | |
| 0.7.10 | 6 / 2 | |
| 0.7.9 | 6 / 2 | |
| 0.7.8 | 6 / 2 | |
| 0.7.7 | 6 / 2 | |
| 0.7.6 | 6 / 2 | |
| 0.7.5 | 6 / 2 | |
| 0.7.4 | 6 / 2 | |
| 0.7.3 | 6 / 2 | |
| 0.7.2 | 6 / 2 | |
| 0.6.15 | 6 / 2 | |
| 0.6.14 | 6 / 2 | |
| 0.6.13 | 6 / 2 | |
| 0.6.12 | 6 / 2 | |
| 0.6.11 | 6 / 2 | |
| 0.6.9 | 6 / 2 | |
| 0.6.8 | 6 / 2 | |
| 0.6.7 | 6 / 2 | |
| 0.6.6 | 6 / 2 | |
| 0.6.5 | 6 / 2 | |
| 0.6.4 | 6 / 2 | |
| 0.6.3 | 6 / 2 | |
| 0.6.2 | 6 / 2 | |
| 0.6.1 | 6 / 2 | |
| 0.5.11 | 6 / 2 | |
| 0.5.10 | 6 / 2 | |
| 0.5.9 | 6 / 2 | |
| 0.5.8 | 6 / 2 | |
| 0.5.7 | 6 / 2 | |
| 0.5.6 | 6 / 2 | |
| 0.5.5 | 6 / 2 | |
| 0.5.4 | 6 / 2 | |
| 0.5.3 | 6 / 2 | |
| 0.5.2 | 6 / 2 | |
| 0.5.1 | 6 / 2 | |
| 0.5.0 | 6 / 2 | |
| 0.4.18 | 6 / 2 | |
| 0.4.17 | 6 / 2 | |
| 0.4.16 | 6 / 2 | |
| 0.4.15 | 6 / 2 |
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (super_oleg) than the most recent previously approved version (tinkoffbank) on 2023-08-14, but super_oleg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.