@rescui/typography
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): Internal JetBrains UI library; sparse metadata is expected for org-scoped packages across all versions. | ai | |
| phantom-deps | phantom-dep:@rescui/colors | AI (phantom-deps): Same org scope; likely used in CSS/PostCSS build pipeline rather than direct JS import. | ai | |
| phantom-deps | phantom-dep:inter-ui | AI (phantom-deps): Font package referenced in CSS build pipeline, not JS imports; stable pattern for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.27.2 | 4 / 7 | |
| 0.27.1 | 4 / 7 | |
| 0.27.0 | 4 / 7 | |
| 0.26.0 | 4 / 7 | |
| 0.25.0 | 4 / 7 | |
| 0.24.4 | 4 / 7 | |
| 0.24.3 | 4 / 7 | |
| 0.24.2 | 4 / 7 | |
| 0.24.0 | 4 / 7 | |
| 0.23.2 | 4 / 7 | |
| 0.23.1 | 4 / 7 | |
| 0.23.0 | 4 / 7 | |
| 0.22.0 | 4 / 7 | |
| 0.21.1 | 4 / 7 | |
| 0.21.0 | 4 / 7 | |
| 0.20.0 | 4 / 7 | |
| 0.19.1 | 4 / 7 | |
| 0.19.0 | 4 / 7 | |
| 0.18.2 | 4 / 7 | |
| 0.18.1 | 4 / 7 | |
| 0.18.0 | 4 / 7 | |
| 0.17.0 | 4 / 7 | |
| 0.16.4 | 5 / 7 | |
| 0.16.3 | 5 / 7 | |
| 0.16.2 | 5 / 7 | |
| 0.16.1 | 5 / 7 | |
| 0.16.0 | 5 / 7 | |
| 0.15.0 | 4 / 7 | |
| 0.14.0 | 4 / 7 | |
| 0.13.0 | 4 / 7 |
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
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.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.2
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.0
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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.