bayareawebpro/laravel-dom-pipeline
A clear README, MIT licensing, repository tests, and release notes make the package easy to evaluate and integrate. Limited recent activity, minimal adoption, no security policy, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
65%
Total Score
50
100
83
83
Health Score Breakdown
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing redundancy if that person becomes unavailable.
The registry namespace and repository are owned by the same individual account, supporting clear ownership, though there is no organization backing to add maintainer depth.
The project is over six years old with nine releases, but only one release in the last 12 months and a typical gap of about four months indicate a modest maintenance cadence.
The repository recorded no commits and no active maintainers during the last three months, a concrete sign that maintenance has currently slowed.
There are no open issues or pull requests, but there was also no issue or pull-request activity in the past month, so this does not demonstrate an active community.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dan Alvidrez |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/pipeline Version ^12.0|^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 months ago
- Created
- 6 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.