@jbrowse/react-linear-genome-view2
JBrowse 2 linear genome view React component
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD; SLSA provenance confirms automated publish. | ai | |
| source-diff | net-exec-file:dist/react-linear-genome-view.umd.production.min.js | AI (source-diff): Standard webpack UMD production bundle for a complex React component; network+exec is inherent to the app. | ai | |
| source-diff | source-size-tripled | AI (source-diff): New UMD bundle added to dist/; expected for a genome viewer shipping a complete production build. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Same as @emotion/cache — MUI peer dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a transitive peer dep used by @jbrowse/* internals; not directly imported in this wrapper package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/cache — MUI peer dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; stable false positive for compiled TS packages. | ai | |
| phantom-deps | phantom-dep:@emotion/cache | AI (phantom-deps): Emotion packages are config-referenced MUI peer deps; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 28 / 0 | |
| 4.2.1 | 28 / 0 | |
| 4.2.0 | 28 / 0 | |
| 4.1.15 | 28 / 0 | |
| 4.1.1 | 28 / 0 | |
| 4.0.4 | 28 / 0 | |
| 4.0.3 | 28 / 0 | |
| 4.0.2 | 28 / 0 | |
| 4.0.1 | 28 / 0 | |
| 4.0.0 | 28 / 0 |
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
3 findingsThis version was published by a different npm account than previous versions on 2026-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
3 findingsThis version was published by a different npm account than previous versions on 2026-04-16. This could indicate a legitimate maintainer transition or an account compromise.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.15
2 findingsNewly 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.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.