@rescui/chip-list
* [Usage examples of TabList](./docs/demo.md) * [Usage examples of ChipList](./docs/chip-list/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; sparse metadata is consistent across all 127 versions of this monorepo package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this JetBrains internal component package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 2 / 4 | |
| 0.14.1 | 2 / 4 | |
| 0.14.0 | 2 / 4 | |
| 0.13.6 | 2 / 4 | |
| 0.13.5 | 2 / 4 | |
| 0.13.4 | 2 / 4 | |
| 0.13.3 | 2 / 4 | |
| 0.13.2 | 2 / 4 | |
| 0.13.1 | 2 / 4 | |
| 0.13.0 | 2 / 4 | |
| 0.12.4 | 2 / 4 | |
| 0.12.3 | 2 / 4 | |
| 0.12.2 | 2 / 4 | |
| 0.12.1 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.5 | 2 / 4 | |
| 0.11.4 | 2 / 4 | |
| 0.11.3 | 2 / 4 | |
| 0.11.2 | 2 / 4 | |
| 0.11.1 | 3 / 4 | |
| 0.11.0 | 4 / 4 | |
| 0.10.0 | 4 / 4 | |
| 0.9.11 | 4 / 4 | |
| 0.9.10 | 4 / 4 | |
| 0.9.9 | 4 / 4 | |
| 0.9.8 | 4 / 4 | |
| 0.9.7 | 4 / 4 | |
| 0.9.6 | 4 / 4 | |
| 0.9.5 | 5 / 4 | |
| 0.9.4 | 5 / 4 | |
| 0.9.3 | 5 / 4 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
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.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.