silexlabs/amfphp

The linked project is backed by an organization and includes tests, a changelog, and a detected BSD-3-Clause license. Its repository is not archived, but recent commit and issue activity is absent, so future maintenance is uncertain.

Latest v2.2.2

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than 10 years, with zero releases in the last 12 months. This is strong evidence of stagnation for a dependency that may need compatibility or security updates.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old registry release, this raises a meaningful risk of abandonment.

Repo issue activity

There were no new or closed issues or pull requests in the last month, with only three open issues and one open pull request. This suggests little active maintenance or community response.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a minor transparency gap rather than a severe concern because the project has a linked repository and established packaging structure.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This matters more for a server-side remoting library, which may expose network-facing functionality.