nepada/phone-number-doctrine
Clear documentation, repository tests, and release notes make the package straightforward to evaluate and adopt. The single-maintainer project also lacks a security policy, while its workflow audit found a medium-confidence bot-condition issue.
68%
Total Score
75
100
100
50
Health Score Breakdown
There were no commits and no active maintainers in the last three months. This lowers confidence in ongoing maintenance, although the repository was pushed recently and had two merged pull requests in the last month.
No security policy is present. This is a transparency gap for a library, though it is not by itself evidence of unsafe code or abandonment.
All 8 action references are unpinned, which weakens build reproducibility. The audit also found one medium-confidence, high-severity bot-condition pattern; because it is a workflow hygiene issue without an untrusted trigger or checkout sink, it warrants caution rather than danger.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Petr Morávek |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 doctrine/dbal Version ^3.4@dev || ^4.0@dev | — | — |
brick/phonenumber Version ^0.2.2@dev || ^0.3@dev || ^0.4@dev || ^0.5@dev || ^0.6@dev || ^0.7@dev || ^0.8@dev | — | — |
Weekly Downloads
Info
- Last Published
- 11 months ago
- Created
- 8 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.