@jbrowse/plugin-spreadsheet-view
JBrowse 2 spreadsheet view
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @jbrowse/* scoped packages replacing equivalent removed deps; not third-party. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 402 approved packages; dormancy consistent with major version gap (3.x to 4.x) in a monorepo. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): mobx is a declared runtime dep in a MobX-state-tree plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs declared as runtime dep; used transitively in jbrowse monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@gmod/bgzf-filehandle | AI (phantom-deps): Declared runtime dep in monorepo plugin; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@jbrowse/plugin-linear-genome-view | AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, phantom-dep is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 11 / 0 | |
| 4.1.14 | 11 / 0 | |
| 4.1.12 | 11 / 0 | |
| 4.1.8 | 11 / 0 | |
| 3.7.0 | 13 / 0 |
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.14
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.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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.