@jbrowse/plugin-gff3
JBrowse 2 gff3.
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): Maintainer removal consistent with transition to automated CI publishing under GitHub Actions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active monorepo package; dormancy signal is a false positive for packages published on-demand with releases. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with monorepo CI/CD migration. | ai | |
| phantom-deps | phantom-dep:@jbrowse/plugin-linear-genome-view | AI (phantom-deps): Same-org plugin dependency; monorepo pattern, stable across versions. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): Config-referenced UI dependency; stable pattern for this plugin. | ai | |
| phantom-deps | phantom-dep:@gmod/bgzf-filehandle | AI (phantom-deps): Config-referenced data-handling dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): mobx is a declared runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@flatten-js/interval-tree | AI (phantom-deps): Declared runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 7 / 0 | |
| 4.2.0 | 7 / 0 | |
| 4.1.15 | 7 / 0 | |
| 4.1.14 | 7 / 0 | |
| 4.1.13 | 7 / 0 | |
| 4.1.12 | 7 / 0 | |
| 4.1.11 | 7 / 0 | |
| 4.1.10 | 7 / 0 | |
| 4.1.9 | 7 / 0 | |
| 4.1.8 | 7 / 0 | |
| 4.1.7 | 7 / 0 | |
| 4.1.6 | 7 / 0 | |
| 4.1.5 | 7 / 0 | |
| 4.1.4 | 7 / 0 | |
| 4.1.3 | 7 / 0 | |
| 4.1.2 | 7 / 0 | |
| 4.1.1 | 7 / 0 | |
| 4.1.0 | 7 / 0 | |
| 4.0.4 | 7 / 0 | |
| 4.0.3 | 7 / 0 | |
| 4.0.2 | 7 / 0 | |
| 4.0.1 | 7 / 0 | |
| 4.0.0 | 7 / 0 | |
| 3.7.0 | 10 / 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.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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.