@outlit/pi
Pi package for Outlit customer intelligence tools
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:pg | AI (typosquat): @outlit/pi is a scoped package with a legitimate product name; Levenshtein match to 'pg' is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @outlit/pi; 2-edit distance match to 'hapi' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @outlit/pi; 2-edit distance match to 'qs' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @outlit/pi; 2-edit distance match to 'joi' is a false positive with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @outlit/pi; 2-edit distance match to 'pino' is a false positive with no impersonation intent. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 1 / 6 | |
| 0.1.3 | 1 / 6 | |
| 0.1.2 | 1 / 6 | |
| 0.1.1 | 1 / 6 | |
| 0.1.0 | 1 / 6 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage name '@outlit/pi' is 1 edit(s) away from popular package 'pg'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.