@jbrowse/plugin-wiggle
JBrowse 2 wiggle adapters, tracks, etc.
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; stable pattern for this monorepo going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with shift to automated CI publishing; no malicious indicators. | ai | |
| provenance | missing-githead | AI (provenance): Established JBrowse2 monorepo package; missing gitHead is a CI config change, not a security risk for this publisher. | ai | |
| phantom-deps | phantom-dep:colord | AI (phantom-deps): colord is a declared runtime dep used in build output; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/file-saver-es | AI (phantom-deps): Type-only package; not imported at runtime by design, stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 18 / 0 | |
| 4.2.1 | 18 / 0 | |
| 4.2.0 | 18 / 0 | |
| 4.1.15 | 18 / 0 | |
| 4.1.14 | 18 / 0 | |
| 4.1.13 | 18 / 0 | |
| 4.1.12 | 18 / 0 | |
| 4.1.11 | 18 / 0 | |
| 4.1.10 | 18 / 0 | |
| 4.1.9 | 18 / 0 | |
| 4.1.8 | 18 / 0 | |
| 4.1.7 | 18 / 0 | |
| 4.1.6 | 18 / 0 | |
| 4.1.5 | 18 / 0 | |
| 4.1.4 | 18 / 0 | |
| 4.1.3 | 18 / 0 | |
| 4.1.1 | 18 / 0 | |
| 4.0.4 | 18 / 0 | |
| 4.0.3 | 18 / 0 | |
| 4.0.2 | 18 / 0 | |
| 4.0.1 | 18 / 0 | |
| 4.0.0 | 18 / 0 | |
| 3.7.0 | 16 / 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
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
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.
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.
Package 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.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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.