contentpulseio/laravel

Usable with caveats: it has a matching repository, clear documentation, tests, and very recent development. It is still a young v0.1 package with rapid releases, concentrated contributions, and no documented security policy or scanning.

Latest v0.1.33

Packagist

70%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, and the repository is owned by a user account; this supports identity continuity but does not provide the resilience of organization backing.

Release history

There have been 33 releases in 100 days, with the latest released today, showing active development but also a very rapid release cadence for a young package.

Repo bus factor

One contributor made 29 of 33 recent commits, leaving maintenance heavily concentrated despite a second contributor being active; the repository owner is an individual account, so there is no organizational backing to offset this concentration.

Repo tooling

Composer is used as the build tool, but no security scanning tools were detected, leaving a gap in visible security-maintenance practice.

Security policy

The repository has no security policy, so users lack documented guidance for reporting vulnerabilities and understanding the project's security response.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

ContentPulse

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/console Version ^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/routing Version ^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/support Version ^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/database Version ^10.0\|^11.0\|^12.0\|^13.0	—	—