@jitsu/js
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:qs | AI (typosquat): Scoped package @jitsu/js is the legitimate Jitsu analytics SDK; Levenshtein match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Same false positive pattern; @jitsu/js is an established scoped package unrelated to jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false positive pattern; unrelated to pg. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Same false positive pattern; unrelated to rxjs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false positive pattern; unrelated to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same false positive pattern; unrelated to ajv. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.10.4 | 1 / 25 | |
| 1.10.3 | 1 / 25 | |
| 1.10.2 | 1 / 25 | |
| 1.10.1 | 1 / 25 |
v1.10.4
2 findingsPackage name '@jitsu/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.