marrios/firulincore

The package is licensed, documented, and has a small dependency footprint without install-time scripts. Limited security tooling and a very small project footprint make long-term maintenance and review harder.

Latest v1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about four years ago, with no releases in the last 12 months. That strongly raises abandonment risk despite the stable v1.0.0 version.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old release history, this is strong evidence of an inactive project.

Maintainers

Only one registry account has publishing access. With a user-owned project and no evidence of a broader active maintainer base, this increases continuity risk if that maintainer stops work.

Project backing

The repository owner is an individual rather than an organization, and the registry has a single maintainer. The available backing evidence therefore does not show organizational continuity.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a meaningful hygiene gap for a dependency intended for reuse.