@rescui/card
`cardCn` is a style generator to create styled card on top of chosen tag.
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): Established JetBrains UI component library; sparse metadata is a stable pattern across all @rescui/* packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal component library; missing description is a stable pattern for this package family. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Babel runtime is injected by the build toolchain, not directly imported; stable false positive for transpiled packages. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @rescui/card is a JetBrains design system component; Levenshtein match to 'cors' is coincidental. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.14.4 | 2 / 7 | |
| 0.14.3 | 2 / 7 | |
| 0.14.2 | 2 / 7 | |
| 0.14.1 | 2 / 7 | |
| 0.14.0 | 2 / 7 | |
| 0.13.13 | 2 / 7 | |
| 0.13.12 | 2 / 7 | |
| 0.13.11 | 2 / 7 | |
| 0.13.10 | 2 / 7 | |
| 0.13.9 | 2 / 7 | |
| 0.13.8 | 2 / 7 | |
| 0.13.7 | 2 / 7 | |
| 0.13.6 | 2 / 7 | |
| 0.13.5 | 2 / 7 | |
| 0.13.4 | 2 / 7 | |
| 0.13.3 | 2 / 7 | |
| 0.13.2 | 2 / 7 | |
| 0.13.1 | 2 / 7 | |
| 0.13.0 | 2 / 7 | |
| 0.12.0 | 2 / 6 | |
| 0.11.6 | 2 / 6 | |
| 0.11.5 | 2 / 6 | |
| 0.11.4 | 2 / 6 | |
| 0.11.3 | 2 / 6 | |
| 0.11.2 | 2 / 6 | |
| 0.11.1 | 2 / 6 | |
| 0.11.0 | 2 / 6 | |
| 0.10.12 | 2 / 6 | |
| 0.10.11 | 2 / 6 | |
| 0.10.10 | 3 / 6 | |
| 0.10.9 | 3 / 6 | |
| 0.10.8 | 3 / 6 | |
| 0.10.7 | 3 / 6 | |
| 0.10.6 | 3 / 6 | |
| 0.10.5 | 3 / 6 | |
| 0.10.4 | 3 / 6 | |
| 0.10.3 | 3 / 6 | |
| 0.10.2 | 3 / 6 | |
| 0.10.1 | 3 / 6 | |
| 0.10.0 | 3 / 6 | |
| 0.9.4 | 3 / 6 | |
| 0.9.3 | 3 / 6 | |
| 0.9.2 | 3 / 6 |
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.