lokijs
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
techfort
Keywords
javascriptdocument-orientedmmdbjsonnosqllokijsin-memoryindexeddb
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:log4js | AI (typosquat): lokijs is a well-known in-memory DB package, not a typosquat of log4js; distinct brand with 4680-day history. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to deserialize S3-stored database content; legitimate data handling, not payload obfuscation. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.5.12 | 0 / 14 |
v1.5.12
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.