isapp/laravel-cart

Usable with caveats: the package has a clear MIT license, documentation, tests, and matching organization-backed source repository, but it has had no new release or repository commits for about 13 months. Lack of security scanning and a security policy adds transparency risk for a Laravel application dependency.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, published about 13 months ago, with no releases in the last 12 months. This leaves limited evidence of ongoing release maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the one-release history, this is the main evidence that maintenance may have stalled.

Repo issue activity

There are no open issues or pull requests and no activity in the last month. While this may reflect a small or quiet project, it provides no evidence of active community maintenance.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers confidence in external adoption but does not independently make the package unsafe to depend on.

Repo tooling

Composer is used as a build tool, but no security scanning tools are present. The absence of scanning is a transparency gap, though it is not by itself evidence of malicious behavior.