Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com
76%
Total Score
healthy
Regular releases and active commits support the package, while single-person maintenance and unclear repository ownership add caution.
The release has no build attestation and does not use staged publishing. This is a transparency gap, although the package has a clear license and active source repository to provide some context.
Only one account has registry publish access, matching the single active repository contributor. This is not evidence of inactivity, but it leaves release continuity dependent on one person.
The repository owner is an individual user rather than an organization. Combined with one active contributor, this provides no organizational succession signal.
One contributor made all 76 commits in the last 3 months, giving the project a single-person bus factor. The active commit volume helps, but there is no second active contributor to provide continuity.
The repository name does not match the package name, and the README has no confirmed mention of the package. A name mismatch can be normal for a monorepo, but the absent confirmation makes the source relationship less transparent.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tslib Version >=2.8.1 | — | — |
upath2 Version ^3.1.25 | — | — |
pkg-dir Version <6 >=5 | — | — |
micromatch Version ^4.0.8 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.