fileset

Release historydanger

The package has had no release for nearly ten years, despite 14 releases overall. This is strong evidence of possible abandonment for a dependency at this version.

Maintainerscaution

Only one registry account has publish access. This is a modest resilience concern for an independently owned package because publishing continuity depends on a single account.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating no current maintenance activity.

Repo toolingcaution

The repository uses Make and Babel, showing a defined build process, but it reports no security scanning tools. That is a modest hygiene gap, not evidence that the release is unsafe.

Security policycaution

The repository has no security policy. This reduces transparency about vulnerability reporting and handling, though it is less significant for a small, mature utility than evidence of active maintenance would be.