select

Release historydanger

The package has had no release since February 2017, more than 9 years before collection, and has had zero releases in the last 12 months. This is the main abandonment concern despite its long history and 13 total releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release gap and indicating little current maintenance capacity.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, so consumers cannot verify how the registry artifact was produced. The package's simple, dependency-free artifact partly limits the practical impact.

Repo toolingcaution

The repository uses npm scripts for builds, but no security scanning tools were detected. That reduces ongoing visibility into dependency and code risks.

Security policycaution

No security policy was found, leaving vulnerability reporting and response expectations undocumented. This is a hygiene concern rather than evidence of unsafe code.