erbitron/dialog-esms

Project backingcaution

The registry package and repository are associated with different namespaces and the repository is user-owned rather than organization-owned. The repository does explicitly identify and document the package, so this is context for a small maintainer base rather than evidence of a mismatch.

Release historycaution

The package is only 76 days old and has two releases, both within the last year; this is too little history to establish long-term maintenance reliability.

Repo bus factorcaution

All recent commits come from a single contributor, leaving the project dependent on one person's availability and increasing continuity risk.

Repo commit activitycaution

There was one commit in the last three months from one active maintainer. Recent activity is present, but the very low volume provides limited evidence of sustained maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The missing scan is a modest transparency gap rather than a standalone health failure.