The package is small and tested, with a recent stable release, matching source repository, and no install scripts. Its missing security policy and limited repository activity leave less evidence of ongoing maintenance.
68%
Total Score
50
100
88
75
Only one registry account has publish access, creating a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of a broader maintainer capacity to offset that risk.
The registry namespace and repository owner match, and the repository is user-owned. The matching ownership supports attribution, but does not show organizational backing.
The package has existed for about four years with six releases, one in the last 12 months, and a median interval of about 224 days. This indicates ongoing but infrequent maintenance rather than a highly active release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. This is meaningful evidence of currently slow maintenance, although it is partly offset by the recent package release and repository push.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
osynapsy/sql Version ^1.0 | — | — |
osynapsy/active-record Version ^1.0 | — | — |
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.