nagnit4enko/ispmanager-api

Release historydanger

The package has only one release, published in January 2023, and none in the following 1,339 days. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance activity.

Maintainerscaution

A single registry maintainer is consistent with the repository being owned by an individual, but it leaves little visible publishing redundancy if that maintainer stops supporting the package.

Project backingcaution

The package and repository are owned by the same individual account, providing consistent ownership context but no organizational backing to compensate for the inactive project.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of abandonment by itself.