← Home

@jbrowse/react-linear-genome-view2

JBrowse 2 linear genome view React component

22
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

garrettjstevensrbuelscmdcolin

Keywords

jbrowsejbrowse2

Accepted risks

Findings the reviewer chose to accept rather than block on.

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

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.14 28 / 0
4.1.13 28 / 0
4.1.12 28 / 0
4.1.11 28 / 0
4.1.10 28 / 0
4.1.9 28 / 0
4.1.8 28 / 0
4.1.7 28 / 0
4.1.6 28 / 0
4.1.5 28 / 0
4.1.4 28 / 0
4.1.3 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.1.14

1 finding
LOW No provenance attestation provenance

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

v4.1.13

1 finding
LOW No provenance attestation provenance

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

v4.1.12

1 finding
LOW No provenance attestation provenance

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

v4.1.11

1 finding
LOW No provenance attestation provenance

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

v4.1.10

1 finding
LOW No provenance attestation provenance

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

v4.1.9

1 finding
LOW No provenance attestation provenance

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

v4.1.8

1 finding
LOW No provenance attestation provenance

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

v4.1.7

1 finding
LOW No provenance attestation provenance

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

v4.1.6

1 finding
LOW No provenance attestation provenance

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

v4.1.5

1 finding
LOW No provenance attestation provenance

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

v4.1.4

1 finding
LOW No provenance attestation provenance

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

v4.1.3

1 finding
LOW No provenance attestation provenance

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