← Home

cytoscape

npm Repository Homepage

Graph theory (a.k.a. network) library for analysis and visualisation

65
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cytoscapenpmmaxkfranzdylanfongmikekucerachrtannus

Keywords

graphgraph-theorynetworknodeedgevertexlinkanalysisvisualisationvisualizationdrawrenderbiojscytoscape

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 65 of 265)

Version Deps Published
2.7.1 0 / 41
2.7.0 0 / 41
2.6.12 0 / 47
2.6.11 0 / 47
2.6.10 0 / 47
2.6.9 0 / 47
2.6.8 0 / 47
2.6.7 0 / 47
2.6.6 0 / 47
2.6.5 0 / 47
2.6.4 0 / 47
2.6.3 0 / 47
2.6.2 0 / 47
2.6.1 0 / 47
2.6.0 0 / 47
2.5.5 0 / 47
2.5.4 0 / 47
2.5.3 0 / 47
2.5.2 0 / 47
2.5.1 0 / 47
2.5.0 0 / 47
2.4.9 0 / 34
2.4.8 0 / 34
2.4.7 0 / 34
2.4.6 0 / 34
2.4.5 0 / 34
2.4.4 0 / 31
2.4.3 0 / 31
2.4.2 0 / 31
2.4.1 0 / 31
2.4.0 0 / 31
2.3.16 0 / 25
2.3.15 0 / 25
2.3.14 0 / 25
2.3.13 0 / 25
2.3.11 0 / 25
2.3.10 0 / 25
2.3.9 0 / 25
2.3.8 0 / 25
2.3.7 0 / 25
2.3.6 0 / 25
2.3.5 0 / 22
2.3.4 0 / 22
2.3.3 0 / 22
2.3.1 0 / 22
2.3.0 0 / 22
2.2.14 0 / 21
2.2.13 0 / 21
2.2.12 0 / 21
2.2.11 0 / 21
2.2.10 0 / 21
2.2.9 0 / 21
2.2.8 0 / 19
2.2.7 0 / 19
2.2.6 0 / 17
2.2.5 0 / 17
2.2.4 0 / 16
2.2.3 0 / 16
2.2.2 0 / 14
2.2.1 0 / 12
2.2.0 0 / 12
2.1.1 0 / 2
2.1.0 0 / 2
2.0.5 0 / 0
2.0.3 0 / 0

v2.7.1

1 finding
INFO No provenance attestation provenance

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

v2.7.0

1 finding
INFO No provenance attestation provenance

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

v2.6.12

1 finding
INFO No provenance attestation provenance

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

v2.6.11

1 finding
INFO No provenance attestation provenance

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

v2.6.10

1 finding
INFO No provenance attestation provenance

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

v2.6.9

1 finding
INFO No provenance attestation provenance

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

v2.6.8

1 finding
INFO No provenance attestation provenance

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

v2.6.7

1 finding
INFO No provenance attestation provenance

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

v2.6.6

1 finding
INFO No provenance attestation provenance

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

v2.6.5

1 finding
INFO No provenance attestation provenance

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

v2.6.4

1 finding
INFO No provenance attestation provenance

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

v2.6.3

1 finding
INFO No provenance attestation provenance

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

v2.6.2

1 finding
INFO No provenance attestation provenance

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

v2.6.1

1 finding
INFO No provenance attestation provenance

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

v2.6.0

1 finding
INFO No provenance attestation provenance

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

v2.5.5

1 finding
INFO No provenance attestation provenance

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

v2.5.4

1 finding
INFO No provenance attestation provenance

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

v2.5.3

1 finding
INFO No provenance attestation provenance

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

v2.5.2

1 finding
INFO No provenance attestation provenance

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

v2.5.1

1 finding
INFO No provenance attestation provenance

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

v2.5.0

1 finding
INFO No provenance attestation provenance

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

v2.4.9

1 finding
INFO No provenance attestation provenance

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

v2.4.8

1 finding
INFO No provenance attestation provenance

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

v2.4.7

1 finding
INFO No provenance attestation provenance

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

v2.4.6

1 finding
INFO No provenance attestation provenance

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

v2.4.5

1 finding
INFO No provenance attestation provenance

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

v2.4.4

1 finding
INFO No provenance attestation provenance

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

v2.4.3

1 finding
INFO No provenance attestation provenance

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

v2.4.2

1 finding
INFO No provenance attestation provenance

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

v2.4.1

1 finding
INFO No provenance attestation provenance

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

v2.4.0

1 finding
INFO No provenance attestation provenance

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

v2.3.16

1 finding
INFO No provenance attestation provenance

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

v2.3.15

1 finding
INFO No provenance attestation provenance

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

v2.3.14

1 finding
INFO No provenance attestation provenance

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

v2.3.13

1 finding
INFO No provenance attestation provenance

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

v2.3.11

1 finding
INFO No provenance attestation provenance

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

v2.3.10

1 finding
INFO No provenance attestation provenance

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

v2.3.9

1 finding
INFO No provenance attestation provenance

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

v2.3.8

1 finding
INFO No provenance attestation provenance

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

v2.3.7

1 finding
INFO No provenance attestation provenance

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

v2.3.6

1 finding
INFO No provenance attestation provenance

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

v2.3.5

1 finding
INFO No provenance attestation provenance

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

v2.3.4

1 finding
INFO No provenance attestation provenance

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

v2.3.3

1 finding
INFO No provenance attestation provenance

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

v2.3.1

1 finding
INFO No provenance attestation provenance

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

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.14

1 finding
INFO No provenance attestation provenance

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

v2.2.13

1 finding
INFO No provenance attestation provenance

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

v2.2.12

1 finding
INFO No provenance attestation provenance

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

v2.2.11

1 finding
INFO No provenance attestation provenance

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

v2.2.10

1 finding
INFO No provenance attestation provenance

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

v2.2.9

1 finding
INFO No provenance attestation provenance

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

v2.2.8

1 finding
INFO No provenance attestation provenance

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

v2.2.7

1 finding
INFO No provenance attestation provenance

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

v2.2.6

1 finding
INFO No provenance attestation provenance

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

v2.2.5

1 finding
INFO No provenance attestation provenance

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

v2.2.4

1 finding
INFO No provenance attestation provenance

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

v2.2.3

1 finding
INFO No provenance attestation provenance

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

v2.2.2

1 finding
INFO No provenance attestation provenance

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

v2.2.1

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.1

1 finding
INFO No provenance attestation provenance

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

v2.1.0

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.3

3 findings
HIGH dll-injection-apis: src/extensions/compound/newawt/Toolkit.js:2 semgrep

DLL injection API detected — potential process injection attack 1 | Clazz.declarePackage ("newawt"); > 2 | Clazz.load (["java.awt.AWTEventMulticaster", "java.awt.event.AWTEventListener", "java.beans.PropertyChangeSupport", "jav 3 | c$ = Clazz.decorateAsClass (function () { 4 | this.desktopProperties = null;

HIGH dll-injection-apis: src/extensions/compound/newawt/Toolkit.js:189 semgrep

DLL injection API detected — potential process injection attack 187 | function () { 188 | if (!newawt.Toolkit.loaded) { > 189 | java.security.AccessController.doPrivileged ( new sun.security.action.LoadLibraryAction ("awt")); 190 | ($t$ = newawt.Toolkit.loaded = true, newawt.Toolkit.prototype.loaded = newawt.Toolkit.loaded, $t$); 191 | }});

INFO No provenance attestation provenance

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