← Home

cytoscape-cose-bilkent

npm Repository Homepage

The CoSE layout for Cytoscape.js by Bilkent with enhanced compound node placement

7
Versions
MIT
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

balcihasancytoscapenpmdylanfongmaxkfranzmetincansipermj3cheunugurdogrusoz

Keywords

cytoscapecytoscape-extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process usage is in gulpfile.js (dev build tooling only), not in runtime code. Standard pattern for gulp-based build scripts; no risk to package consumers. ai
provenance publisher-changed AI (provenance): Publisher change occurred in 2017; dylanfong has 291 approved packages and is part of the official cytoscape org. Legitimate long-standing maintainer transition. ai

Versions (showing 7 of 7)

Version Deps Published
4.1.0 1 / 16
4.0.0 0 / 14
3.0.4 1 / 18
3.0.3 1 / 18
3.0.2 1 / 18
3.0.1 1 / 18
3.0.0 1 / 18

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: dylanfong → balcihasan (on 2017-11-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-29. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.3

2 findings
HIGH Publisher changed: balcihasan → dylanfong (on 2017-11-28) provenance

This version was published by a different npm account than previous versions on 2017-11-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.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.