The small codebase is clearly packaged, tested, licensed, and matched to its repository. Its five-year maintenance gap and lack of security policy leave adoption dependent on the package remaining stable without active fixes.
58%
Total Score
67
100
79
88
The repository is owned by an individual account rather than an organization, so the thin maintainer base is not offset by visible organizational backing.
The latest release was July 2021, with no releases in the last 12 months and only six releases overall. This is a meaningful maintenance concern for a dependency, although the stable release may still meet a narrow, unchanged need.
The repository had zero commits and zero active maintainers in the last three months, consistent with the long release gap. This raises abandonment and response-time risk.
The repository has two stars and no forks, showing a very small user and contributor footprint. Popularity is only supporting evidence, but this provides little external maintenance capacity.
Composer build tooling is present, but no security-scanning tools are configured. For a small library this is a modest transparency and maintenance gap, not a standalone severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
opis/json-schema 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.