awsmug/torro-forms

Tests, a changelog, release notes, and a matching repository provide useful maintenance evidence. The last registry release was about six years ago, with no recent commits or issue activity, and the workflows use unpinned actions including one archived action. The missing security policy further limits transparency.

Latest 1.0.8

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about six years ago, and there were no releases in the last 12 months. The 19-release history shows the project was previously active but is now stale.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. Combined with the old release history, this is strong evidence of abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 76 issues remain open. This indicates little visible current project activity.

Repo tooling

The repository uses Composer build tooling, but no security scanning tools were detected. The lack of scanning weakens security hygiene, though it is not by itself evidence that the package is unsafe.

Security policy

No security policy was found in the repository, leaving no documented process for reporting or handling vulnerabilities.