caprel/dolibarr-stubs

The package is focused and transparent, with a clear README, MIT license, no runtime dependencies, and no install-time scripts. Its repository remains linked and unarchived, but community activity is minimal and no security policy is provided.

Latest v18.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has five releases but none in the last 12 months, and its latest release was over two years ago. This materially increases maintenance and abandonment risk for a versioned stub package.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive for over two years. This is the strongest abandonment concern.

Project backing

The package is tied to a user-owned repository rather than an organization, so the small maintainer base offers limited visible project backing.

Repo popularity

The repository has one star, no forks, and one watcher. Popularity is only supporting evidence, but this very small audience provides little external maintenance or review signal.

Repo tooling

The repository uses Composer build tooling, which fits the package, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.