cytoscape
Graph theory (a.k.a. network) library for analysis and visualisation
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dll-injection-apis | AI (semgrep): Flagged file is a Java-to-JS transpiled class loader (Clazz framework). Clazz.load() is not a DLL injection API; stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Occurs in bundled jQuery 1.9.1's JSON parsing fallback — a well-known, intentional pattern. Not a supply-chain risk for cytoscape. | ai | |
| license | uncommon-license:LGPL-3.0+ | AI (license): LGPL-3.0+ is a well-known GNU Lesser GPL license; the 'uncommon' flag is a false positive for this valid SPDX identifier. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(10) is a numeric module ID generated by browserify bundling — a stable false positive pattern in browserified code, not arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process.fork() spawns cytoscape's own thread-node-fork.js for parallel computation. Explicitly stubbed out in browser builds via package.json browser field. Legitimate and documented. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used in cytoscape's thread worker to execute serialized user-provided functions for parallel graph computation — a documented, intentional API feature, not a supply-chain risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New lodash sub-packages (get/set/topath) are canonical, well-established utilities fully consistent with a graph library's needs. No malicious signal. | ai | |
| dependencies | unvetted-dep:lodash.set | AI (dependencies): lodash.set is a well-known lodash utility that has been a stable runtime dependency of cytoscape across many versions; not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Cytoscape.js is a 12-year-old established library; lack of Sigstore provenance is expected and not a risk signal for this package. | ai | |
| source-diff | net-exec-file:dist/cytoscape.esm.mjs | AI (source-diff): This is the ESM distribution bundle of Cytoscape.js with MIT copyright header. Network/dynamic patterns are legitimate library features, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/cytoscape.esm.min.mjs | AI (source-diff): This is a minified ESM build of the Cytoscape.js graph library. Network APIs and dynamic patterns are legitimate library features (AJAX data loading, Babel polyfills), not malware. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The raw IP (127.0.0.1) appears only in Playwright test files as a localhost reference for the local http-server used during testing — entirely benign for this package. | ai |
Versions (showing 100 of 265)
| Version | Deps | Published |
|---|---|---|
| 3.33.4 | 0 / 33 | |
| 3.33.3 | 0 / 33 | |
| 3.33.2 | 0 / 33 | |
| 3.33.1 | 0 / 33 | |
| 3.33.0 | 0 / 33 | |
| 3.32.2 | 0 / 33 | |
| 3.32.1 | 0 / 33 | |
| 3.32.0 | 0 / 33 | |
| 3.31.4 | 0 / 33 | |
| 3.31.2 | 0 / 33 | |
| 3.31.1 | 0 / 33 | |
| 3.31.0 | 0 / 30 | |
| 3.30.4 | 0 / 29 | |
| 3.30.3 | 0 / 29 | |
| 3.30.2 | 0 / 29 | |
| 3.30.1 | 0 / 29 | |
| 3.30.0 | 0 / 29 | |
| 3.29.3 | 0 / 29 | |
| 3.29.2 | 0 / 29 | |
| 3.29.1 | 0 / 29 | |
| 3.29.0 | 0 / 29 | |
| 3.28.1 | 2 / 27 | |
| 3.28.0 | 2 / 27 | |
| 3.27.2 | 2 / 27 | |
| 3.27.1 | 2 / 27 | |
| 3.27.0 | 2 / 27 | |
| 3.26.2 | 2 / 27 | |
| 3.26.1 | 2 / 27 | |
| 3.26.0 | 2 / 27 | |
| 3.25.2 | 2 / 27 | |
| 3.25.1 | 2 / 27 | |
| 3.25.0 | 2 / 27 | |
| 3.24.2 | 2 / 27 | |
| 3.24.1 | 2 / 27 | |
| 3.24.0 | 2 / 27 | |
| 3.23.1 | 2 / 27 | |
| 3.23.0 | 2 / 27 | |
| 3.22.1 | 2 / 27 | |
| 3.22.0 | 5 / 27 | |
| 3.21.3 | 2 / 27 | |
| 3.21.2 | 5 / 28 | |
| 3.21.1 | 5 / 28 | |
| 3.21.0 | 5 / 28 | |
| 3.20.3 | 2 / 28 | |
| 3.20.2 | 2 / 28 | |
| 3.20.1 | 2 / 28 | |
| 3.20.0 | 2 / 28 | |
| 3.19.1 | 2 / 28 | |
| 3.19.0 | 2 / 28 | |
| 3.18.3 | 2 / 28 | |
| 3.18.2 | 2 / 28 | |
| 3.18.1 | 2 / 28 | |
| 3.18.0 | 2 / 28 | |
| 3.17.4 | 2 / 28 | |
| 3.17.3 | 2 / 28 | |
| 3.17.2 | 2 / 28 | |
| 3.17.1 | 2 / 28 | |
| 3.17.0 | 2 / 28 | |
| 3.16.5 | 2 / 28 | |
| 3.16.4 | 2 / 28 | |
| 3.16.3 | 2 / 28 | |
| 3.16.2 | 2 / 28 | |
| 3.16.1 | 2 / 28 | |
| 3.16.0 | 2 / 28 | |
| 3.15.5 | 2 / 28 | |
| 3.15.4 | 2 / 28 | |
| 3.15.3 | 2 / 28 | |
| 3.15.2 | 2 / 28 | |
| 3.15.1 | 2 / 28 | |
| 3.15.0 | 2 / 28 | |
| 3.14.4 | 2 / 28 | |
| 3.14.3 | 2 / 28 | |
| 3.14.2 | 2 / 28 | |
| 3.14.1 | 2 / 28 | |
| 3.14.0 | 2 / 28 | |
| 3.13.3 | 2 / 28 | |
| 3.13.2 | 2 / 28 | |
| 3.13.1 | 2 / 28 | |
| 3.13.0 | 2 / 28 | |
| 3.12.3 | 2 / 28 | |
| 3.12.2 | 2 / 28 | |
| 3.12.1 | 2 / 28 | |
| 3.12.0 | 2 / 28 | |
| 3.11.2 | 2 / 28 | |
| 3.11.1 | 2 / 28 | |
| 3.11.0 | 2 / 28 | |
| 3.10.2 | 2 / 28 | |
| 3.10.1 | 2 / 28 | |
| 3.10.0 | 2 / 28 | |
| 3.9.4 | 2 / 31 | |
| 3.9.3 | 2 / 31 | |
| 3.9.2 | 2 / 31 | |
| 3.9.1 | 2 / 31 | |
| 3.9.0 | 2 / 31 | |
| 3.8.5 | 2 / 31 | |
| 3.8.4 | 2 / 31 | |
| 3.8.3 | 2 / 31 | |
| 3.8.2 | 2 / 31 | |
| 3.8.1 | 2 / 31 | |
| 3.8.0 | 2 / 31 |
v3.33.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.33.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. 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.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.