dam2k/ampmailer

The project has had no commits in three months and only one release, so its maintenance track record is still unproven. A complete README, repository tests, MIT licensing, and no install-time scripts provide useful safeguards, but the two unpinned workflow actions and missing security policy leave notable hygiene gaps.

Latest 0.6.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so the project does not show organizational backing to compensate for its limited history.

Release history

This release is from a package only 132 days old with one release total, so there is not enough history to establish a dependable maintenance pattern.

Repo commit activity

There were zero commits and zero active maintainers during the last three months, a meaningful warning for a package whose only release is also its initial release.

Repo issue activity

There has been no issue or pull-request activity in the last month; with no broader history, this provides little evidence of an active support cycle.

Repo popularity

The repository has zero stars, forks, and watchers, so there is no community adoption signal to offset the short maintenance history, though popularity alone is not decisive.