Package Health/amaxlab/tocan-notifications

amaxlab/tocan-notifications

The MIT license and two runtime dependencies make basic adoption straightforward. The organization-owned repository provides some ownership context, but no security policy is documented.

Latest v1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published about 11 years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a library expected to receive maintenance.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, consistent with its last push in 2015. There is no provided activity suggesting ongoing maintenance.

Package scaffolding

The artifact has no README, tests, or changelog, and the repository also reports no tests or changelog. Missing tests and project documentation materially reduce confidence for a reusable payment-events library, although the GitHub release confirms the version was published.

Repo popularity

The repository has 0 stars and 0 forks, with only 2 watchers. Popularity is supporting evidence rather than a verdict, but these counts provide no meaningful community or adoption signal to offset the age and inactivity.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tool is configured. The missing scanning is a modest hygiene concern rather than proof that the release is unsafe.