to-no-case

Release historydanger

The package has had no release in nearly 10 years; its latest release was October 2016, despite a long history and seven total releases. This is strong evidence of inactive maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided signal shows current maintenance capacity.

Repo issue activitycaution

There was no issue or pull request activity in the last month, with one issue still open. This supports the conclusion that the project is inactive, though the small package scope limits the severity.

Repository archivedcaution

The linked repository is not archived, although its last push was in October 2016. The active archive status is mildly reassuring but does not offset the observed inactivity.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities or handling security issues. The package's simple scope partly limits the practical impact.