@outlit/core
Shared types and utilities for Outlit tracking SDKs
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:cors | AI (typosquat): @outlit/core is a scoped package for the Outlit AI SDK, not a typosquat of cors. The name similarity is coincidental and the package has a clear, legitimate identity. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.5 | 0 / 4 | |
| 1.4.3 | 0 / 4 | |
| 1.1.0 | 0 / 4 | |
| 1.0.1 | 0 / 3 | |
| 1.0.0 | 0 / 3 | |
| 0.4.0 | 0 / 3 | |
| 0.3.0 | 0 / 3 | |
| 0.2.2 | 0 / 3 | |
| 0.2.1 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.0 | 0 / 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
2 findingsPackage name '@outlit/core' is 1 edit(s) away from popular package 'cors'.
Package 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.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.