@starasia/text
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 | no-provenance | AI (provenance): Small UI component package; lack of Sigstore provenance is a process gap, not a security risk for this package. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped UI component package; name similarity to 'next' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped UI component package; name similarity to 'nuxt' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped UI component package; name similarity to 'jest' is coincidental, not impersonation. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 0 / 11 | |
| 3.0.0 | 0 / 11 | |
| 2.0.0 | 0 / 11 | |
| 1.0.5 | 0 / 11 | |
| 1.0.4 | 0 / 11 | |
| 1.0.3 | 0 / 11 | |
| 1.0.2 | 0 / 11 | |
| 1.0.1 | 0 / 11 | |
| 1.0.0 | 0 / 11 |
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rizkyizh.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rizkyizh.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.