ixixx
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to spawn 'sort' for trix index building; benign and stable for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread used only to pass locale override to child sort process; no exfiltration risk. | ai | |
| phantom-deps | phantom-dep:@jbrowse/quick-lru | AI (phantom-deps): Declared as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.9 | 1 / 13 | |
| 3.0.7 | 1 / 13 | |
| 3.0.6 | 1 / 13 | |
| 3.0.5 | 1 / 13 | |
| 3.0.4 | 4 / 13 | |
| 3.0.3 | 3 / 13 | |
| 3.0.2 | 4 / 13 | |
| 3.0.1 | 4 / 12 | |
| 3.0.0 | 4 / 12 |
v3.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.