after

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing signal to offset the thin recent maintenance evidence.

Release historycaution

The package has 19 releases, but its latest release was in August 2016 and it had no releases in the last 12 months. That long release gap is evidence of weak ongoing maintenance.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, while the repository was last pushed in 2020. This confirms that maintenance has been inactive for a prolonged period.

Repo toolingcaution

The repository uses no build tooling and has no security scanning tools. The simple source tree makes the lack of a build system reasonable, but the absence of security scanning reduces assurance.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.