Determine where a ts type declaration comes from
58%
Total Score
caution
Usable with caveats: release and commit activity have stopped, despite a documented and stable project.
No build attestation, trusted publisher, or staged publishing is reported, reducing release transparency even though this is not evidence that the package is unsafe.
A prepare install-time script adds supply-chain and installation complexity, although it is common for packages that build or prepare artifacts.
Only one registry account has publish access, leaving a thin publishing base; the repository is user-owned, so there is no organizational backing signal to offset that concern.
The repository is owned by an individual rather than an organization, so long-term continuity depends on a single project owner.
The package has eight releases over roughly two years, but it has had no releases in the last 12 months, indicating slowed maintenance for a relatively young package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
picomatch Version ^4.0.2 | — | — |
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.