@rescui/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): JetBrains internal UI component library; sparse metadata is consistent across all 110 versions. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared in dependencies; used by runtime/build. False positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Declared in dependencies; loaded by convention. False positive for this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.13.7 | 3 / 6 | |
| 0.13.6 | 3 / 6 | |
| 0.13.5 | 3 / 6 | |
| 0.13.4 | 3 / 6 | |
| 0.13.3 | 3 / 6 | |
| 0.13.2 | 3 / 6 | |
| 0.13.1 | 3 / 6 | |
| 0.13.0 | 3 / 6 | |
| 0.12.2 | 3 / 6 | |
| 0.12.1 | 3 / 6 | |
| 0.12.0 | 3 / 6 | |
| 0.11.0 | 3 / 6 | |
| 0.10.17 | 3 / 6 | |
| 0.10.16 | 3 / 6 | |
| 0.10.15 | 3 / 6 | |
| 0.10.14 | 3 / 6 | |
| 0.10.13 | 3 / 6 | |
| 0.10.12 | 3 / 6 | |
| 0.10.11 | 3 / 6 | |
| 0.10.10 | 3 / 6 | |
| 0.10.9 | 4 / 6 | |
| 0.10.8 | 4 / 6 | |
| 0.10.7 | 4 / 6 | |
| 0.10.6 | 4 / 6 | |
| 0.10.5 | 4 / 6 | |
| 0.10.4 | 4 / 6 | |
| 0.10.3 | 4 / 6 | |
| 0.10.2 | 4 / 6 | |
| 0.10.1 | 4 / 6 | |
| 0.10.0 | 4 / 6 | |
| 0.9.8 | 4 / 6 | |
| 0.9.7 | 4 / 6 | |
| 0.9.6 | 4 / 6 |
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.