@nivo/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, 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): @nivo/text is a scoped sub-package of the nivo monorepo; no impersonation of 'next'. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @nivo/text is a scoped sub-package of the nivo monorepo; no impersonation of 'nuxt'. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @nivo/text is a scoped sub-package of the nivo monorepo; no impersonation of 'jest'. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 3 / 0 | |
| 0.98.0 | 3 / 0 | |
| 0.97.0 | 3 / 0 | |
| 0.96.0 | 3 / 0 | |
| 0.95.0 | 3 / 0 | |
| 0.94.0 | 3 / 0 | |
| 0.93.0 | 2 / 0 | |
| 0.92.1 | 2 / 0 | |
| 0.92.0 | 2 / 0 | |
| 0.91.0 | 2 / 0 | |
| 0.90.0 | 2 / 0 | |
| 0.89.1 | 2 / 0 | |
| 0.89.0 | 2 / 0 | |
| 0.88.0 | 2 / 0 | |
| 0.87.0 | 2 / 0 |
v0.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.