reinterval

Release historydanger

The latest of only four releases was published in June 2016, with no releases in the last 12 months. This long release gap is strong evidence of reduced maintenance, although the package may be intentionally stable.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the last push being over six years ago, this indicates a sustained lack of active maintenance.

Build provenancecaution

No build attestation or trusted-publisher provenance is available. This limits publication transparency, but the package is a small JavaScript artifact with no install lifecycle scripts, so the impact is limited.

Maintainerscaution

Registry publishing access is held by one user account. That is a narrow operational base, though the repository is also owned by the same individual, so the finding is a moderate capacity concern rather than evidence of a mismatch.

Project backingcaution

The repository is owned by an individual user rather than an organization. That is consistent with the single-maintainer profile and provides no institutional continuity if the maintainer stops contributing.