sendery/symfony

Documentation, tests, and release notes make the integration easier to evaluate. The project is brand new, with only one release and no recorded commits in the last three months. Its workflow uses read-only permissions but leaves both action references unpinned, and no security scanning is configured.

Latest v0.1.0

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's first release, published within the last day, so there is no release cadence or track record yet. That limits evidence of maturity but is expected for a newly launched package.

Repo commit activity

No commits and no active maintainers were recorded during the last three months. Because the package was first released within the last day, this is more a lack of history than evidence of abandonment, but it still leaves maintenance capacity unproven.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and hygiene gap for a package handling mail credentials.

Security policy

The repository has no security policy. For a new integration that requires an API key, this weakens the documented vulnerability-reporting path.

Version stability

Version 0.1.0 is not a stable major release, which signals an early API and compatibility stage. It is not marked as a prerelease, providing some compensation but not a long-term stability record.