@rescui/tag
* [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 — 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 internal UI component library; sparse metadata is consistent across all @rescui/* packages. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped JetBrains design system package; no plausible impersonation of the postgres 'pg' client. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.13.7 | 3 / 3 | |
| 0.13.6 | 3 / 3 | |
| 0.13.5 | 3 / 3 | |
| 0.13.4 | 3 / 3 | |
| 0.13.3 | 3 / 3 | |
| 0.13.2 | 3 / 3 | |
| 0.13.1 | 3 / 3 | |
| 0.13.0 | 3 / 3 | |
| 0.12.1 | 3 / 3 | |
| 0.12.0 | 3 / 3 | |
| 0.11.3 | 3 / 3 | |
| 0.11.2 | 3 / 3 | |
| 0.11.1 | 3 / 3 | |
| 0.11.0 | 3 / 3 | |
| 0.10.21 | 3 / 3 | |
| 0.10.20 | 3 / 3 | |
| 0.10.19 | 3 / 3 | |
| 0.10.18 | 3 / 3 |
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.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.