@eclipse-scout/migrate
TypeScript migration module
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:ts-migrate | AI (dependencies): ts-migrate is a well-known Microsoft OSS tool; stable dependency for this migration package. | ai | |
| dependencies | unvetted-dep:ts-migrate-server | AI (dependencies): ts-migrate-server is part of the same Microsoft ts-migrate monorepo; stable for this package. | ai | |
| dependencies | unvetted-dep:ts-migrate-plugins | AI (dependencies): ts-migrate-plugins is part of the same Microsoft ts-migrate monorepo; stable for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 26.1.16 | 6 / 6 | |
| 26.1.15 | 6 / 6 | |
| 26.1.12 | 6 / 6 | |
| 26.1.9 | 6 / 6 | |
| 26.1.7 | 6 / 6 | |
| 26.1.6 | 6 / 6 | |
| 26.1.3 | 6 / 6 | |
| 26.1.1 | 6 / 6 | |
| 25.2.20 | 6 / 6 | |
| 25.2.16 | 6 / 6 | |
| 25.2.15 | 6 / 6 | |
| 25.2.14 | 6 / 6 |
v26.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.