@outlit/node
Outlit server-side tracking SDK for Node.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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @outlit/node is a scoped analytics SDK from Outlit AI with a clear identity and GitHub repo; Levenshtein proximity to 'zod' is coincidental and not indicative of impersonation. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 1 / 4 | |
| 1.4.5 | 1 / 4 | |
| 1.4.3 | 1 / 3 | |
| 1.4.2 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.1 | 1 / 3 | |
| 1.0.0 | 1 / 3 | |
| 0.4.0 | 1 / 3 | |
| 0.3.0 | 1 / 3 | |
| 0.2.2 | 1 / 3 | |
| 0.2.1 | 1 / 3 | |
| 0.2.0 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.