@jbrowse/react-app2
JBrowse 2 app 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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/react-app.umd.production.min.js | AI (source-diff): Long encoded strings are expected in webpack UMD minified bundles for this genomics visualization library; stable false positive. | ai | |
| source-diff | net-exec-file:dist/react-app.umd.production.min.js | AI (source-diff): UMD production bundle for a genomics app; network+eval patterns are from CSS-in-JS and worker infrastructure, not malware. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects bundling all @jbrowse plugins into a UMD dist; expected for this package type. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is a legitimate supply-chain improvement. | ai | |
| phantom-deps | phantom-dep:@emotion/cache | AI (phantom-deps): Declared as peer/transitive dep for MUI theming; config-file reference is expected pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established JBrowse monorepo; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): MUI requires @emotion/react; config-file reference is standard. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI requires @emotion/styled; config-file reference is standard. | ai | |
| phantom-deps | phantom-dep:@types/file-saver-es | AI (phantom-deps): Type-only package; framework-scoped, not directly imported at runtime. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 45 / 0 | |
| 4.2.1 | 45 / 0 | |
| 4.2.0 | 45 / 0 | |
| 4.1.15 | 45 / 0 | |
| 4.1.1 | 45 / 0 | |
| 4.0.4 | 45 / 0 | |
| 4.0.3 | 45 / 0 | |
| 4.0.2 | 45 / 0 | |
| 4.0.1 | 45 / 0 | |
| 4.0.0 | 45 / 0 |
v4.3.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published 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.
[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.