deprecation

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no demonstrated organizational backing to offset the thin maintenance evidence.

Release historycaution

The latest release was published in June 2019, with no releases in the last 12 months. This is a meaningful maintenance concern for a package last updated about 7 years ago.

Repo commit activitycaution

The repository recorded 0 commits and 0 active maintainers over the last 3 months. Combined with the long release gap, this lowers confidence in ongoing maintenance.

Repo toolingcaution

The project uses npm scripts for builds but reports no security scanning tools. This is a modest transparency and maintenance gap, not a standalone adoption blocker.

Security policycaution

The repository has no security policy. For a small utility this is not severe, but it leaves vulnerability reporting and response expectations undocumented.