The project has a long history, a current release, tests, release notes, and organization backing. One contributor carries all recent commits, while all three workflow actions are unpinned and no security policy is provided.
78%
Total Score
83
94
75
All 10 recent commits came from one contributor, giving the project a single-person operational dependency. Organization backing provides some handoff capacity, but no second active contributor is shown.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools are reported. This is a modest transparency gap rather than evidence of unsafe maintenance.
The repository has no security policy. For a database access library this reduces clarity about vulnerability reporting and response, though it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. All 3 of 3 action references are unpinned, leaving avoidable update and supply-chain hygiene risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
xp-framework/core Version ^12.11 | ^11.11 | — | — |
xp-framework/math Version ^10.0 | ^9.0 | ^8.0 | ^7.0 | — | — |
xp-framework/logging Version ^11.0 | ^10.0 | ^9.0 | ^8.0 | ^7.0 | — | — |
xp-framework/networking Version ^11.0 | ^10.0 | ^9.3 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.