← Home

tsconfig-paths-webpack-plugin

Load modules according to tsconfig paths in webpack.

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

timmotoorassvazlafiljohkahdividstefansvenssoneriengjohankristianssonadam.luotonenjonaskellobjolindgeonmarsvehenbrjosef.dagsonoskdah

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:eval-usage AI (semgrep): All 14 hits are in temp/bundle.js — standard webpack devtool eval wrapping in test fixtures, not malicious code. ai
dependencies unvetted-dep:tapable AI (dependencies): Core webpack package by the webpack team; expected dependency for a webpack plugin. ai
dependencies unvetted-dep:enhanced-resolve AI (dependencies): Core webpack resolver package; expected dependency for a webpack resolver plugin. ai
dependencies unvetted-dep:tsconfig-paths AI (dependencies): Companion library by the same author (dividab); the core path-resolution engine this plugin wraps. ai

Versions (showing 2 of 2)

Version Deps Published
4.2.0 4 / 19
4.0.0 3 / 19

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.