@studyportals/multiselect
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@studyportals/styles-abstracts | AI (phantom-deps): Same-org style dependency consumed via CSS/webpack, not direct JS import; stable pattern for this UI component package. | ai | |
| phantom-deps | phantom-dep:@studyportals/styles-components | AI (phantom-deps): Same-org style dependency consumed via CSS/webpack, not direct JS import; stable pattern for this UI component package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.3.5 | 3 / 10 | |
| 4.3.4 | 3 / 10 | |
| 4.3.3 | 3 / 10 | |
| 4.3.1 | 3 / 14 | |
| 4.3.0 | 3 / 14 |
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.