@jbrowse/plugin-trix
JBrowse 2 trix text search 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 | missing-githead | AI (provenance): Trusted publisher with long track record; missing gitHead is a CI config change, not a security risk for this package. | ai | |
| dependencies | unvetted-dep:@jbrowse/core | AI (dependencies): First-party JBrowse ecosystem dependency; stable false positive for all @jbrowse/* packages. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): Listed as a real runtime dependency in package.json; stable false positive for this monorepo plugin. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): Listed as a real runtime dependency in package.json; stable false positive for this monorepo plugin. | ai | |
| phantom-deps | phantom-dep:mobx-state-tree | AI (phantom-deps): Listed as a real runtime dependency in package.json; stable false positive for this monorepo plugin. | ai | |
| phantom-deps | phantom-dep:mobx-react | AI (phantom-deps): Listed as a real runtime dependency in package.json; stable false positive for this monorepo plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established JBrowse monorepo package; absence of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 2 / 0 | |
| 4.2.1 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.15 | 2 / 0 | |
| 4.1.14 | 2 / 0 | |
| 4.1.13 | 2 / 0 | |
| 4.1.12 | 2 / 0 | |
| 4.1.11 | 2 / 0 | |
| 4.1.10 | 2 / 0 | |
| 4.1.9 | 2 / 0 | |
| 4.1.8 | 2 / 0 | |
| 4.1.7 | 2 / 0 | |
| 4.1.6 | 2 / 0 | |
| 4.1.5 | 2 / 0 | |
| 4.1.4 | 2 / 0 | |
| 4.1.3 | 2 / 0 | |
| 4.1.1 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.4 | 2 / 0 | |
| 4.0.3 | 2 / 0 | |
| 4.0.2 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.7.0 | 6 / 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
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
1 findingPublished 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
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
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
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.