@jbrowse/plugin-gtf
JBrowse 2 gtf feature adapter
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): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with monorepo automation for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals accompany shift to CI-based publishing; not indicative of takeover for this established package. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): UI dep declared for config/type resolution; stable false positive for JBrowse plugins. | ai | |
| phantom-deps | phantom-dep:@gmod/bgzf-filehandle | AI (phantom-deps): Declared dep used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): JBrowse plugins declare mobx as a dep for type resolution; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@flatten-js/interval-tree | AI (phantom-deps): Declared dep used in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jbrowse/plugin-linear-genome-view | AI (phantom-deps): Same-org sibling dep; stable false positive for JBrowse monorepo plugins. | ai | |
| phantom-deps | phantom-dep:@jbrowse/mobx-state-tree | AI (phantom-deps): Same-org dep declared for type resolution; stable false positive for JBrowse monorepo plugins. | ai | |
| phantom-deps | phantom-dep:mobx-react | AI (phantom-deps): Same pattern as mobx; declared for type/config resolution in JBrowse plugin monorepo. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 10 / 0 | |
| 4.2.1 | 10 / 0 | |
| 4.2.0 | 10 / 0 | |
| 4.1.15 | 10 / 0 | |
| 4.1.14 | 10 / 0 | |
| 4.1.13 | 10 / 0 | |
| 4.1.12 | 10 / 0 | |
| 4.1.11 | 10 / 0 | |
| 4.1.10 | 10 / 0 | |
| 4.1.9 | 10 / 0 | |
| 4.1.8 | 10 / 0 | |
| 4.1.7 | 10 / 0 | |
| 4.1.6 | 10 / 0 | |
| 4.1.5 | 10 / 0 | |
| 4.1.4 | 10 / 0 | |
| 4.1.3 | 10 / 0 | |
| 4.1.1 | 10 / 0 | |
| 4.0.4 | 10 / 0 | |
| 4.0.3 | 10 / 0 | |
| 4.0.2 | 10 / 0 | |
| 4.0.1 | 10 / 0 | |
| 4.0.0 | 10 / 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.1
2 findingsThis 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
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. Consider requesting the maintainer enable provenance via CI/CD.
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. 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.