@rescui/dropdown
* [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): Established JetBrains scoped UI component; sparse metadata is consistent across all 118 versions of this internal library. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 7 / 5 | |
| 0.10.3 | 6 / 5 | |
| 0.10.2 | 6 / 5 | |
| 0.10.1 | 6 / 5 | |
| 0.10.0 | 6 / 5 | |
| 0.9.7 | 6 / 5 | |
| 0.9.6 | 6 / 5 | |
| 0.9.5 | 6 / 5 | |
| 0.9.4 | 6 / 5 | |
| 0.9.3 | 6 / 5 | |
| 0.9.2 | 6 / 5 | |
| 0.9.1 | 6 / 5 | |
| 0.9.0 | 6 / 5 | |
| 0.8.4 | 6 / 5 | |
| 0.8.3 | 6 / 5 | |
| 0.8.2 | 6 / 5 | |
| 0.8.1 | 6 / 5 | |
| 0.8.0 | 6 / 5 | |
| 0.7.22 | 6 / 5 | |
| 0.7.21 | 6 / 5 | |
| 0.7.20 | 6 / 5 | |
| 0.7.19 | 6 / 5 | |
| 0.7.18 | 6 / 5 | |
| 0.7.17 | 6 / 5 | |
| 0.7.16 | 6 / 5 | |
| 0.7.15 | 6 / 5 | |
| 0.7.14 | 6 / 5 | |
| 0.7.13 | 6 / 5 | |
| 0.7.12 | 6 / 5 | |
| 0.7.11 | 7 / 5 | |
| 0.7.10 | 7 / 5 | |
| 0.7.9 | 7 / 5 | |
| 0.7.8 | 7 / 5 | |
| 0.7.7 | 7 / 5 | |
| 0.7.6 | 7 / 5 | |
| 0.7.5 | 7 / 5 | |
| 0.7.4 | 7 / 5 | |
| 0.7.3 | 7 / 4 | |
| 0.7.2 | 7 / 4 | |
| 0.7.1 | 7 / 4 | |
| 0.7.0 | 7 / 4 | |
| 0.6.4 | 7 / 4 | |
| 0.6.3 | 7 / 4 | |
| 0.6.2 | 7 / 4 |
v0.11.0
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.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.