typescript-transform-paths
Transforms module resolution paths using TypeScript path mapping and/or custom paths
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from danielpanpm to nonara (Ron S.) occurred in 2021; nonara is listed as a contributor in package.json and has a strong track record (46 approved packages). Legitimate maintainer transition, stable across many versions. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 3.4.7 | 1 / 12 | |
| 3.4.6 | 1 / 12 | |
| 3.4.5 | 1 / 12 | |
| 3.4.4 | 1 / 12 | |
| 3.4.3 | 1 / 12 | |
| 3.4.2 | 1 / 12 | |
| 3.4.1 | 1 / 12 | |
| 3.4.0 | 1 / 12 | |
| 3.3.1 | 1 / 12 | |
| 3.3.0 | 1 / 12 | |
| 3.2.1 | 1 / 12 | |
| 3.2.0 | 1 / 12 | |
| 3.1.0 | 1 / 13 | |
| 3.0.2 | 1 / 13 | |
| 3.0.1 | 1 / 13 | |
| 3.0.0 | 1 / 13 | |
| 2.2.4 | 1 / 13 | |
| 2.2.3 | 1 / 13 | |
| 2.2.2 | 1 / 13 | |
| 2.2.1 | 1 / 13 | |
| 2.2.0 | 1 / 13 | |
| 2.1.0 | 0 / 12 | |
| 2.0.4 | 0 / 11 | |
| 2.0.3 | 0 / 11 | |
| 2.0.2 | 0 / 11 | |
| 2.0.1 | 0 / 11 | |
| 2.0.0 | 0 / 10 | |
| 1.1.15 | 0 / 9 | |
| 1.1.14 | 1 / 9 | |
| 1.1.13 | 1 / 9 | |
| 1.1.12 | 1 / 9 | |
| 1.1.11 | 1 / 9 | |
| 1.1.10 | 1 / 9 | |
| 1.1.9 | 1 / 9 | |
| 1.1.8 | 1 / 9 | |
| 1.1.7 | 1 / 9 | |
| 1.1.6 | 1 / 9 | |
| 1.1.5 | 1 / 9 | |
| 1.1.4 | 1 / 4 | |
| 1.1.3 | 1 / 4 | |
| 1.1.2 | 1 / 5 | |
| 1.1.1 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.2 | 1 / 5 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2021-08-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-23. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.