license-checker

Release historydanger

The package has 74 releases and a historically regular median interval of about 14 days, but its latest registry release was over seven years ago and there were no releases in the last 12 months. This is a substantial maintenance concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the absent recent registry releases, this indicates effectively dormant development.

Build provenancecaution

No build attestation or trusted-publisher identity is present, leaving publication origin less verifiable. This is a transparency weakness, though not severe enough to outweigh the package's other evidence alone.

Maintainerscaution

Only one registry account has publish access. The linked project is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual account, not an organization, so there is no organizational backing shown to compensate for the thin maintainer base.