@lumiarq/ai
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:hapi | AI (typosquat): Scoped package @lumiarq/ai bears no semantic or visual resemblance to 'hapi'; Levenshtein match is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @lumiarq/ai bears no resemblance to 'pg'; short-name Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @lumiarq/ai bears no resemblance to 'qs'; short-name Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lumiarq/ai bears no resemblance to 'joi'; short-name Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @lumiarq/ai bears no resemblance to 'ajv'; short-name Levenshtein match is a false positive. | ai |
v1.2.0
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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.