zareismail/chapar

Release historydanger

The package has had no release in more than five years, despite 12 releases during its initial development period; this is a substantial abandonment concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of current maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected; this is a maintenance and transparency gap for a package handling application code.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but its last push was in March 2021 and does not offset the prolonged inactivity.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; the package's small scope provides some context but does not compensate for the gap.