← Home

tsconfig-paths

npm Repository Homepage

Load node modules according to tsconfig paths, in run-time or via API.

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

johkahdividstefansvenssoneriengjohankristianssonadam.luotonenjonaskellojontembjolindgeonmarsvehenbrjosef.dagsonoskdahcspotcode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require() is used to load package.json files from disk as part of tsconfig path resolution — this is the core intended functionality of the package, not a security risk. ai

Versions (showing 3 of 3)

Version Deps Published
4.2.0 3 / 19
4.1.2 3 / 19
4.0.0 3 / 19

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.