@jbrowse/core
JBrowse 2 core libraries used by plugins
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established JBrowse genome browser core package; scoped name @jbrowse/core has no relation to the cors package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 34 / 0 | |
| 4.2.1 | 34 / 0 | |
| 4.2.0 | 34 / 0 | |
| 4.1.15 | 34 / 0 | |
| 4.1.14 | 34 / 0 | |
| 4.1.13 | 34 / 0 | |
| 4.1.12 | 34 / 0 | |
| 4.1.11 | 34 / 0 | |
| 4.1.10 | 34 / 0 | |
| 4.1.9 | 34 / 0 | |
| 4.1.8 | 34 / 0 | |
| 4.1.7 | 34 / 0 | |
| 4.1.6 | 34 / 0 | |
| 4.1.5 | 34 / 0 | |
| 4.1.4 | 34 / 0 | |
| 4.1.3 | 34 / 0 | |
| 4.1.2 | 34 / 0 | |
| 4.1.1 | 34 / 0 | |
| 4.1.0 | 34 / 0 | |
| 4.0.4 | 35 / 0 | |
| 4.0.3 | 35 / 0 | |
| 4.0.2 | 35 / 0 | |
| 4.0.1 | 35 / 0 | |
| 4.0.0 | 35 / 0 | |
| 3.7.0 | 29 / 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
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.13
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
2 findingsPackage name '@jbrowse/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.