@rescui/select
* [Usage examples](./docs/demo.md)
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal JetBrains UI component library; sparse metadata is consistent across all 128 versions. | ai | |
| dependencies | unvetted-dep:@rescui/tag | AI (dependencies): Sibling @rescui/* package from same JetBrains org; not independently suspicious. | ai | |
| dependencies | unvetted-dep:@rescui/menu | AI (dependencies): Sibling @rescui/* package from same JetBrains org; not independently suspicious. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 8 / 5 | |
| 0.17.3 | 8 / 5 | |
| 0.17.2 | 8 / 5 | |
| 0.17.1 | 8 / 5 | |
| 0.17.0 | 8 / 5 | |
| 0.16.0 | 8 / 5 | |
| 0.15.2 | 8 / 5 | |
| 0.15.1 | 8 / 5 | |
| 0.14.3 | 7 / 5 | |
| 0.14.2 | 7 / 5 | |
| 0.14.1 | 7 / 5 | |
| 0.14.0 | 7 / 5 | |
| 0.13.0 | 7 / 5 | |
| 0.12.3 | 7 / 5 | |
| 0.12.2 | 7 / 5 | |
| 0.12.1 | 7 / 5 | |
| 0.12.0 | 7 / 5 | |
| 0.11.18 | 7 / 5 | |
| 0.11.17 | 7 / 5 | |
| 0.11.16 | 7 / 5 | |
| 0.11.15 | 7 / 5 | |
| 0.11.14 | 7 / 5 | |
| 0.11.13 | 7 / 5 | |
| 0.11.12 | 7 / 5 | |
| 0.11.11 | 7 / 5 | |
| 0.11.10 | 7 / 5 | |
| 0.11.9 | 7 / 5 | |
| 0.11.8 | 7 / 5 | |
| 0.11.7 | 8 / 5 | |
| 0.11.6 | 8 / 5 | |
| 0.11.5 | 8 / 5 | |
| 0.11.4 | 8 / 5 | |
| 0.11.3 | 8 / 5 | |
| 0.11.2 | 8 / 5 | |
| 0.11.1 | 8 / 5 | |
| 0.11.0 | 8 / 5 | |
| 0.10.4 | 9 / 5 | |
| 0.10.3 | 9 / 5 | |
| 0.10.2 | 9 / 5 | |
| 0.10.1 | 9 / 5 | |
| 0.10.0 | 9 / 5 | |
| 0.9.4 | 8 / 7 | |
| 0.9.3 | 8 / 7 | |
| 0.9.2 | 8 / 7 | |
| 0.9.1 | 8 / 7 | |
| 0.9.0 | 8 / 7 |
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.