@semcore/typography
Semrush Typography Component
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): semrushinc is the Semrush org account; legitimate transition from uikit-team. | ai | |
| source-diff | obfuscated-file:lib/cjs/Text.js | AI (source-diff): Long lines are inlined CSS-in-JS strings from reshadow build output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:lib/es6/Text.js | AI (source-diff): Same inlined CSS-in-JS build artifact pattern; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/esm/Text.mjs | AI (source-diff): Same inlined CSS-in-JS build artifact pattern; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@semcore/icon | AI (phantom-deps): @semcore/icon is a same-org dep; phantom-dep false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 0 / 5 | |
| 17.1.0 | 0 / 5 | |
| 17.0.2 | 0 / 5 | |
| 17.0.1 | 0 / 5 | |
| 17.0.0 | 0 / 5 | |
| 16.4.1 | 2 / 3 | |
| 16.4.0 | 2 / 3 | |
| 16.3.2 | 2 / 3 | |
| 5.54.0 | 4 / 2 |
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.54.0
4 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.