@things-factory/kpi
kpi module
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:koa | AI (typosquat): Scoped package @things-factory/kpi; no plausible typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @things-factory/kpi; no plausible typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @things-factory/kpi; no plausible typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @things-factory/kpi; no plausible typosquat of joi. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard migration-file loader pattern; resolves files from a known directory, not user input. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 9.2.27 | 16 / 0 | |
| 9.2.26 | 16 / 0 | |
| 9.2.25 | 16 / 0 | |
| 9.2.19 | 16 / 0 | |
| 9.2.13 | 16 / 0 |
v9.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.