@jbrowse/web-core
JBrowse 2 code shared between web-app type products
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level CI publishing transition for established GMOD/jbrowse-components project. | ai | |
| provenance | publisher-changed | AI (provenance): JBrowse migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD pipeline. | ai | |
| provenance | missing-githead | AI (provenance): Artifact of CI/CD migration; SLSA provenance attestation provides stronger supply chain integrity signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party JBrowse packages and a known UI library; consistent with v4 major refactor. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; conventional usage in transpiled TS packages. | ai | |
| phantom-deps | phantom-dep:copy-to-clipboard | AI (phantom-deps): Declared dep in monorepo package; referenced in config, stable FP. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): JBrowse monorepo package; rxjs is a declared dep used transitively/in config, stable FP. | ai | |
| phantom-deps | phantom-dep:tss-react | AI (phantom-deps): Declared dep in monorepo package; referenced in config, stable FP. | ai | |
| phantom-deps | phantom-dep:mobx-react | AI (phantom-deps): Declared dep in monorepo package; referenced in config, stable FP. | ai | |
| provenance | no-provenance | AI (provenance): Established JBrowse2 monorepo package; provenance absence is consistent across all versions. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 8 / 0 | |
| 4.2.1 | 8 / 0 | |
| 4.2.0 | 8 / 0 | |
| 4.1.15 | 8 / 0 | |
| 4.1.14 | 8 / 0 | |
| 4.1.13 | 8 / 0 | |
| 4.1.12 | 8 / 0 | |
| 4.1.11 | 8 / 0 | |
| 4.1.10 | 8 / 0 | |
| 4.1.9 | 8 / 0 | |
| 4.1.8 | 8 / 0 | |
| 4.1.7 | 8 / 0 | |
| 4.1.6 | 8 / 0 | |
| 4.1.5 | 8 / 0 | |
| 4.1.4 | 8 / 0 | |
| 4.1.3 | 8 / 0 | |
| 4.1.1 | 8 / 0 | |
| 4.0.4 | 8 / 0 | |
| 4.0.3 | 8 / 0 | |
| 4.0.2 | 8 / 0 | |
| 4.0.1 | 8 / 0 | |
| 4.0.0 | 8 / 0 | |
| 3.7.0 | 11 / 0 |
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
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 has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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.
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 has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cmdcolin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.