@rescui/button
* [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 144 versions of this scoped package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this JetBrains scoped component package. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.24.4 | 3 / 6 | |
| 0.24.3 | 3 / 6 | |
| 0.24.2 | 3 / 6 | |
| 0.24.1 | 3 / 6 | |
| 0.24.0 | 3 / 6 | |
| 0.23.6 | 3 / 6 | |
| 0.23.5 | 3 / 6 | |
| 0.23.4 | 3 / 6 | |
| 0.23.3 | 3 / 6 | |
| 0.23.2 | 3 / 6 | |
| 0.23.1 | 3 / 6 | |
| 0.23.0 | 3 / 6 | |
| 0.22.6 | 3 / 6 | |
| 0.22.5 | 3 / 6 | |
| 0.22.4 | 3 / 6 | |
| 0.22.3 | 3 / 6 | |
| 0.22.2 | 3 / 6 | |
| 0.22.1 | 3 / 6 | |
| 0.22.0 | 3 / 6 | |
| 0.21.7 | 3 / 6 | |
| 0.21.6 | 3 / 6 | |
| 0.21.5 | 3 / 6 | |
| 0.21.4 | 3 / 6 | |
| 0.21.3 | 3 / 6 | |
| 0.21.2 | 3 / 6 | |
| 0.21.1 | 3 / 6 | |
| 0.21.0 | 3 / 6 | |
| 0.20.3 | 3 / 6 | |
| 0.20.2 | 3 / 6 | |
| 0.20.1 | 3 / 6 | |
| 0.20.0 | 3 / 6 | |
| 0.19.1 | 3 / 6 | |
| 0.19.0 | 3 / 6 | |
| 0.18.1 | 3 / 6 | |
| 0.18.0 | 4 / 6 | |
| 0.17.1 | 4 / 6 | |
| 0.17.0 | 4 / 6 | |
| 0.16.7 | 4 / 6 | |
| 0.16.6 | 4 / 6 | |
| 0.16.5 | 4 / 6 | |
| 0.16.4 | 4 / 6 | |
| 0.16.3 | 4 / 6 | |
| 0.16.2 | 4 / 6 | |
| 0.16.1 | 4 / 6 | |
| 0.16.0 | 5 / 5 | |
| 0.15.5 | 5 / 5 | |
| 0.15.4 | 5 / 5 | |
| 0.15.3 | 5 / 5 | |
| 0.15.2 | 5 / 5 | |
| 0.15.1 | 5 / 5 | |
| 0.15.0 | 5 / 5 |
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.