cytoscape-dagre
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cytoscape-dagre.js | AI (source-diff): Standard Rollup UMD bundle output; readable code, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cytoscape-dagre.mjs | AI (source-diff): Standard Rollup ESM bundle output; readable code, not obfuscated. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-dormant cytoscape extension revived by original maintainer to migrate to @dagrejs/dagre fork; not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @dagrejs/dagre is the official maintained fork of dagre; this is a straightforward dependency migration. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundling @dagrejs/dagre (larger maintained fork) into the distribution file. | ai |
v4.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.