libpurecontent/application
Regular releases and a push on 29 June 2026 show ongoing maintenance. The five-file project has no tests, security policy, or security scanning, which limits confidence in its long-term resilience.
67%
Total Score
83
94
67
Health Score Breakdown
The artifact and repository each contain five files, including a README, license, Composer manifest, and source file. This is transparent but unusually minimal, leaving little evidence of broader project maturity.
All 3 recent commits came from one contributor, giving the project a single-person operational dependency. Organizational ownership provides some backing, but no second active contributor is shown.
Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tools are detected. That leaves dependency and source-integrity checks less visible.
The repository has no security policy. For a small PHP library this is not an immediate adoption blocker, but it weakens the project's disclosure and response transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 mvl22 |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 pear/mail Version ^2.0 | — | — |
libpurecontent/database Version ^4.2 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 2 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.