split

Release historydanger

The latest release was published in August 2017, and there were no releases in the last 12 months. The long release gap substantially increases abandonment risk despite the package's earlier release history.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. This confirms that the project is not currently receiving maintenance.

Repository archiveddanger

The linked repository is archived, which is a severe abandonment signal for a package developers would newly adopt. Its last push was in July 2019, with no provided evidence of resumed maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while two issues and four pull requests remain open. This is consistent with an inactive project.

Repo toolingcaution

No build tools or security-scanning tools were detected. This is a hygiene gap, though the package is a small JavaScript module and the stronger maintenance signals already determine the assessment.