@jbrowse/plugin-menus
JBrowse 2 basic menus
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): Org migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern for this package going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-wide shift to automated publishing; not indicative of takeover given SLSA attestation and monorepo context. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): mobx is a declared runtime dep in package.json; phantom-dep false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 9 / 0 | |
| 4.2.1 | 9 / 0 | |
| 4.2.0 | 9 / 0 | |
| 4.1.15 | 9 / 0 | |
| 4.1.14 | 9 / 0 | |
| 4.1.13 | 9 / 0 | |
| 4.1.12 | 9 / 0 | |
| 4.1.11 | 9 / 0 | |
| 4.1.10 | 9 / 0 | |
| 4.1.9 | 9 / 0 | |
| 4.1.8 | 9 / 0 | |
| 4.1.7 | 9 / 0 | |
| 4.1.6 | 9 / 0 | |
| 4.1.5 | 9 / 0 | |
| 4.1.4 | 9 / 0 | |
| 4.1.3 | 9 / 0 | |
| 4.1.1 | 9 / 0 | |
| 4.1.0 | 9 / 0 | |
| 4.0.4 | 9 / 0 | |
| 4.0.3 | 9 / 0 | |
| 4.0.2 | 9 / 0 | |
| 4.0.1 | 9 / 0 | |
| 4.0.0 | 9 / 0 | |
| 3.7.0 | 10 / 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.0
2 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.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage 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.1.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.