sledgehammer/filters

Release historydanger

The package has only two releases, and its latest release was over 13 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the short 23-day interval between the original releases.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having been inactive since November 2012. This materially increases the risk that defects and compatibility issues will not be addressed.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security-scanning tooling was detected. This is a secondary transparency and maintenance gap alongside the much older activity record.

Repository archivedcaution

The linked repository is not archived, so it remains administratively available. Its last push was over 13 years ago, however, which limits the reassurance this provides.

Security policycaution

The repository has no security policy. For a small, long-inactive package this reduces the clarity of vulnerability reporting and reinforces the maintenance concern.