← Home

levenshtein

Javascript implementation of the L-diggity.

5
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

gf3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:vendor/qunit-extras/qunit-extras.js AI (source-diff): File is a vendored test utility (QUnit Extras by John-David Dalton) under vendor/; not part of runtime code. Pattern match is a false positive for this test infrastructure file. ai
source-diff source-size-tripled AI (source-diff): Size increase is entirely due to vendored test tooling (qunit.js, qunit-extras.js); core library is unchanged. Not indicative of injected payload. ai
license uncommon-license:Public Domain AI (license): Package uses UNLICENSE (public domain dedication), a well-known and legitimate license. Stable for this package. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.5 0 / 0
1.0.4 0 / 1
1.0.2 0 / 1
1.0.1 0 / 0
1.0.0 0 / 0

v1.0.5

2 findings
HIGH New file with network + code execution: vendor/qunit-extras/qunit-extras.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

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.

v1.0.0

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.