ammarfaizi2/brainly

The MIT license is clear, dependencies are minimal, and the repository matches the package. Its lack of security guidance and very small footprint leave limited evidence of continued oversight.

Latest 1.0.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about six years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository having been inactive for about six years.

Maintainers

Only one registry account has publish access. That is a limited operational base for a user-owned project and increases continuity risk, though it does not prove abandonment alone.

Project backing

The repository is owned by an individual rather than an organization, so there is no shown organizational backing to compensate for the single-maintainer and inactivity concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe behavior.