@rescui/tab-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 — the axios compromise (March 2026) relied on exactly this gap.
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 monorepo component; sparse metadata is a stable pattern across all @rescui/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for @rescui/* scoped packages published from JetBrains monorepo. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.16.6 | 4 / 5 | |
| 0.16.5 | 4 / 5 | |
| 0.16.4 | 4 / 5 | |
| 0.16.3 | 4 / 5 | |
| 0.16.2 | 4 / 5 | |
| 0.16.1 | 4 / 5 | |
| 0.16.0 | 4 / 5 | |
| 0.15.7 | 4 / 5 | |
| 0.15.6 | 4 / 5 | |
| 0.15.5 | 4 / 5 | |
| 0.15.4 | 4 / 5 | |
| 0.15.3 | 4 / 5 | |
| 0.15.2 | 4 / 5 | |
| 0.15.1 | 4 / 5 | |
| 0.15.0 | 4 / 5 | |
| 0.14.7 | 4 / 5 | |
| 0.14.6 | 4 / 5 | |
| 0.14.5 | 4 / 5 | |
| 0.14.4 | 4 / 5 | |
| 0.14.3 | 4 / 5 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.