Package Health

ts-declaration-location

Determine where a ts type declaration comes from

Latest 1.0.7NPMNPM

58%

Total Score

caution

Usable with caveats: release and commit activity have stopped, despite a documented and stable project.

Health Score Breakdown

Build provenancecaution

No build attestation, trusted publisher, or staged publishing is reported, reducing release transparency even though this is not evidence that the package is unsafe.

Lifecycle scriptscaution

A prepare install-time script adds supply-chain and installation complexity, although it is common for packages that build or prepare artifacts.

Maintainerscaution

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.

Project backingcaution

The repository is owned by an individual rather than an organization, so long-term continuity depends on a single project owner.

Release historycaution

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.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Direct Dependencies

DependencyLast ReleaseScore
picomatch
Version ^4.0.2
—
—

Weekly Downloads

Info

Last Published
1 year ago
Created
2 years ago
Unpacked Size
0.1 MB

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform