@tramvai/tools-migrate
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Migration runner loading user-specified migration files by resolved path; expected pattern for this tool. | ai | |
| dependencies | unvetted-dep:@tinkoff/package-manager-wrapper | AI (dependencies): Same-org (@tinkoff) dependency consistent with the tramvai ecosystem; stable pattern across versions. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 0.11.4 | 10 / 3 | |
| 0.11.3 | 10 / 3 | |
| 0.11.2 | 10 / 3 | |
| 0.11.1 | 10 / 3 | |
| 0.10.11 | 10 / 3 | |
| 0.10.10 | 10 / 3 | |
| 0.10.9 | 10 / 3 | |
| 0.10.8 | 10 / 3 | |
| 0.10.7 | 10 / 3 | |
| 0.10.6 | 10 / 3 | |
| 0.10.4 | 10 / 3 | |
| 0.10.3 | 10 / 3 | |
| 0.10.2 | 10 / 3 | |
| 0.9.17 | 10 / 3 | |
| 0.9.16 | 10 / 3 | |
| 0.9.14 | 10 / 3 | |
| 0.9.13 | 10 / 3 | |
| 0.9.12 | 10 / 3 | |
| 0.9.10 | 10 / 3 | |
| 0.9.9 | 10 / 3 | |
| 0.9.8 | 10 / 3 | |
| 0.9.7 | 10 / 3 | |
| 0.9.5 | 10 / 3 | |
| 0.9.4 | 10 / 3 | |
| 0.9.3 | 10 / 3 | |
| 0.9.2 | 10 / 3 | |
| 0.8.16 | 10 / 3 | |
| 0.8.15 | 10 / 3 | |
| 0.8.14 | 10 / 3 | |
| 0.8.13 | 10 / 3 | |
| 0.8.12 | 10 / 3 | |
| 0.8.11 | 10 / 3 | |
| 0.8.9 | 10 / 3 | |
| 0.8.8 | 10 / 3 | |
| 0.8.7 | 10 / 3 | |
| 0.8.6 | 10 / 3 | |
| 0.8.5 | 10 / 3 | |
| 0.8.4 | 10 / 3 | |
| 0.8.3 | 10 / 3 | |
| 0.8.2 | 10 / 3 | |
| 0.8.1 | 10 / 3 | |
| 0.7.11 | 10 / 3 | |
| 0.7.10 | 10 / 3 | |
| 0.7.9 | 10 / 3 | |
| 0.7.8 | 10 / 3 | |
| 0.7.7 | 10 / 3 | |
| 0.7.6 | 10 / 3 | |
| 0.7.5 | 10 / 3 | |
| 0.7.4 | 10 / 3 | |
| 0.7.3 | 10 / 3 | |
| 0.7.2 | 10 / 3 | |
| 0.7.1 | 10 / 3 | |
| 0.7.0 | 10 / 3 | |
| 0.6.23 | 10 / 3 | |
| 0.6.22 | 10 / 3 | |
| 0.6.21 | 10 / 3 | |
| 0.6.20 | 10 / 3 | |
| 0.6.19 | 10 / 3 | |
| 0.6.18 | 10 / 3 | |
| 0.6.17 | 10 / 3 | |
| 0.6.15 | 10 / 3 | |
| 0.6.14 | 10 / 3 | |
| 0.6.13 | 10 / 3 | |
| 0.6.12 | 10 / 3 | |
| 0.6.11 | 10 / 3 | |
| 0.6.10 | 10 / 3 | |
| 0.6.8 | 10 / 3 | |
| 0.6.7 | 10 / 3 | |
| 0.6.6 | 10 / 3 | |
| 0.6.5 | 10 / 3 | |
| 0.6.3 | 10 / 3 | |
| 0.5.139 | 10 / 3 | |
| 0.5.138 | 10 / 3 | |
| 0.5.137 | 10 / 3 | |
| 0.5.136 | 10 / 3 | |
| 0.5.135 | 10 / 3 | |
| 0.5.134 | 10 / 3 | |
| 0.5.133 | 10 / 3 | |
| 0.5.132 | 10 / 3 | |
| 0.5.131 | 10 / 3 | |
| 0.5.130 | 10 / 3 | |
| 0.5.129 | 10 / 3 | |
| 0.5.128 | 10 / 3 | |
| 0.5.127 | 10 / 3 | |
| 0.5.126 | 10 / 3 | |
| 0.5.125 | 10 / 3 | |
| 0.5.124 | 10 / 3 | |
| 0.5.123 | 10 / 3 | |
| 0.5.122 | 10 / 3 | |
| 0.5.121 | 10 / 3 | |
| 0.5.120 | 10 / 3 | |
| 0.5.119 | 10 / 3 | |
| 0.5.118 | 10 / 3 | |
| 0.5.115 | 9 / 3 | |
| 0.5.114 | 9 / 3 |
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
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.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
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.10
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.