@semcore/dot
Semrush Dot 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @semcore package; Levenshtein match to 'got' is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @semcore package; no impersonation of 'koa'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @semcore package; no impersonation of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @semcore package; no impersonation of 'zod'. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 0 / 4 | |
| 17.1.0 | 0 / 4 | |
| 17.0.2 | 0 / 4 | |
| 17.0.1 | 0 / 4 | |
| 17.0.0 | 0 / 4 | |
| 16.1.1 | 3 / 3 | |
| 16.1.0 | 3 / 3 |
v17.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.0
2 findingsPackage name '@semcore/dot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.