solo/app

Release historydanger

The package has had no release in over four years, with zero releases in the last 12 months. That is strong evidence of abandonment despite its long history and earlier regular releases.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided maintenance signal compensates for this inactivity.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package, so the repository may not actually belong to this release.

Repo toolingcaution

Composer build tooling is present, which supports reproducible project structure, but no security scanning tools are configured. The missing security checks modestly reduce maintenance transparency.

Security policycaution

The repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a secondary concern rather than evidence that the package is unsafe.