open20/amos-utility

Licensedanger

No declared license, license file, or repository license file was detected. That creates a material legal and transparency gap for a package intended to be depended on.

Release historydanger

The package has had no release in more than three years, with zero releases in the last 12 months. This is meaningful abandonment risk, although the repository is not archived and the latest version is stable.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little supporting evidence of adoption or community review. Popularity is not decisive, but this weakens confidence in a package already showing inactivity.

Repo toolingcaution

The project uses Composer for builds, which fits the package ecosystem. No security scanning tools were detected, leaving a modest security-process gap.

Security policycaution

The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations, though it is not evidence that the package is unsafe.