madge
1
Versions
—
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
pahenkamiazya
Keywords
ES6ES7AMDRequireJSrequiremodulecirculardependencydependenciesgraphvizgraph
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads local package.json for madge config — benign, stable pattern for this CLI tool. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execFile used to invoke Graphviz for graph rendering — core documented functionality of madge. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 12 / 8 |
v8.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.