jacksonit/esms

Release historydanger

The package has had no release in the last 12 months, and its latest release was over six years ago despite only four releases overall. This is strong evidence of abandonment risk, although the package is not marked deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent maintenance. The repository's non-archived status does not compensate for the absence of activity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, offering no supporting evidence of a broader user or maintainer community. Popularity is only supporting evidence, so this reinforces rather than determines the abandonment concern.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a modest hygiene gap rather than evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For a package with no recent maintenance, this adds to the transparency concern.