t4web/mail

Documentation and test coverage reduce integration risk. Its last release and repository activity date to January 2017, while the dependency set is substantial and security tooling is absent; adopt only if you can maintain compatibility yourself.

Latest 1.0.2

Packagist

35%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than nine years: its latest release was January 2017, with zero releases in the last 12 months. This is strong evidence of abandonment for a dependency users must maintain around.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no observed maintenance capacity.

Dependency profile

The package declares 15 runtime dependencies, including several framework and project-specific components. That increases compatibility and maintenance exposure for an old release.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a standalone reason to reject the package.

Repository archived

The linked repository is not archived, but its last push was January 2017. The active archive status is reassuring, while the old push date reinforces the maintenance concern.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
t4web/crud Version ~1.0.0	—	—
t4web/admin Version dev-master	—	—
t4web/domain-module Version ~1.2.0	—	—
t4web/default-service Version ~1.0.0	—	—
zendframework/zend-db Version ^2.5	—	—