@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 — the axios compromise (March 2026) relied on exactly this gap.
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 18 of 18)
| 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 |
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.