@rescui/dropdown-menu
* [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; sparse metadata is expected for monorepo packages, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Babel runtime injected by build tooling; not directly imported by convention. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.11.18 | 5 / 5 | |
| 0.11.17 | 5 / 5 | |
| 0.11.16 | 5 / 5 | |
| 0.11.15 | 5 / 5 | |
| 0.11.14 | 5 / 5 | |
| 0.11.13 | 5 / 5 | |
| 0.11.12 | 5 / 5 | |
| 0.11.11 | 5 / 5 | |
| 0.11.10 | 5 / 5 | |
| 0.11.9 | 5 / 5 | |
| 0.11.8 | 5 / 5 | |
| 0.11.7 | 5 / 5 | |
| 0.11.6 | 5 / 5 | |
| 0.11.5 | 5 / 5 | |
| 0.11.3 | 5 / 5 | |
| 0.11.2 | 5 / 5 | |
| 0.11.1 | 5 / 5 | |
| 0.11.0 | 5 / 5 | |
| 0.10.0 | 5 / 5 | |
| 0.9.21 | 5 / 5 | |
| 0.9.20 | 5 / 5 | |
| 0.9.19 | 5 / 5 | |
| 0.9.18 | 5 / 5 | |
| 0.9.17 | 5 / 5 | |
| 0.9.16 | 5 / 5 | |
| 0.9.15 | 5 / 5 | |
| 0.9.14 | 5 / 5 | |
| 0.9.13 | 5 / 5 | |
| 0.9.12 | 5 / 5 | |
| 0.9.11 | 6 / 5 | |
| 0.9.10 | 6 / 5 | |
| 0.9.9 | 6 / 5 | |
| 0.9.8 | 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 / 4 | |
| 0.9.2 | 6 / 4 | |
| 0.9.1 | 6 / 4 | |
| 0.9.0 | 6 / 4 | |
| 0.8.5 | 6 / 4 | |
| 0.8.4 | 6 / 4 | |
| 0.8.3 | 6 / 4 |
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.