Package Health/grizzlylab/assets-version-bundle

grizzlylab/assets-version-bundle

Its MIT license, included tests, clear README, and small dependency set make it straightforward to evaluate and integrate. The lack of security scanning and a security policy leaves less assurance for future maintenance.

Latest 2.2.4

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 18 releases but none in the last 12 months, and its latest release was published over five years ago. This is strong evidence of stale maintenance, though the long release history shows it was previously established.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the latest release being over five years old. This materially increases abandonment risk.

Repo issue activity

There was no new issue or pull request activity in the last month and no merged pull requests. Together with the inactive commit signal, this supports a conclusion of limited ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. That weakens ongoing supply-chain and maintenance assurance without making the package unfit by itself.

Security policy

The repository has no security policy, leaving no documented path for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a package intended for application projects.