Package Health/mbezhanov/faker-provider-collection

mbezhanov/faker-provider-collection

Usable with caveats: the package is well documented, tested, licensed, and backed by its matching repository, but it has had no registry release in over two years and no recorded commits in the last three months. Lack of security scanning and a security policy adds a smaller transparency concern.

Latest 2.0.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The project has 11 releases over roughly nine years, but the latest registry release was over two years ago and there were no releases in the last 12 months. That slows confidence in ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers recorded during the last three months. The recent repository push is compensating evidence, but the lack of current activity still raises maintenance risk.

Repo issue activity

There are only two open issues and two open pull requests, but none were created, closed, or merged in the last month, suggesting limited current project activity.

Repo tooling

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

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.