Is aberlaas-lint safe to install?
ASK DepWall stops this install and asks a human.
Checked
against version 2.39.2, using the same engine the CLI runs.
This is a record of one check at one moment — run the gate
for the answer that applies to the version you are about to install.
What the registry says
| Version checked | 2.39.2 |
|---|---|
| Age | 10 days old |
| Weekly downloads | 49 |
| Maintainers | 1 |
| Runs install scripts | no |
| npm provenance | not attested |
| Deprecated | no |
Signals that fired
- warn
maturityvery new (10d) with low adoption (49/wk)
The package is young and has little adoption relative to the name it carries.
What was checked
DepWall reads registry metadata and the package's own manifest before any of its code runs. On npm that means the name against a popularity dictionary and a curated hallucination feed, the tarball hash against OSV's malicious-release advisories, lifecycle scripts, publication age and adoption, provenance attestations across this and prior releases, and dependencies that resolve outside the registry.
It does not execute the package, and this page did not download its source. How verdicts are decided · what this cannot catch.
Check it yourself
npm i -g depwall && depwall init
depwall check aberlaas-lintOnce depwall init has run, the check happens on
npm install itself — including for the transitive dependencies you never
chose, which is where most
of this actually arrives.