Database integration for Joke framework
68%
Total Score
caution
A 34-day-old project has active releases but one-contributor maintenance, no security policy, and unpinned workflow actions.
The package is only 34 days old with three releases, but releases have continued at roughly 17-day intervals, showing active early maintenance rather than abandonment.
All 52 recent commits came from one contributor, creating a meaningful continuity risk; organization ownership provides some handoff capacity but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, which makes vulnerability reporting and disclosure expectations less clear for a database integration package.
The workflow uses read-only permissions and has no dangerous audit findings, but both analyzed action references are unpinned, leaving avoidable workflow reproducibility and supply-chain hygiene risk.
We didn't find any vulnerabilities for this package.
| Version | Published | Vulnerabilities |
|---|---|---|
| 1.0.2 | 15 Oct 2026 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
| 1.0.1 | 10 Sept 2026 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
| 1.0.0 | 10 Sept 2026 | 0 0 critical, 0 total 0 0 high, 0 total 0 0 medium, 0 total 0 0 low, 0 total |
| Dependency | Last Release | Score |
|---|---|---|
voral/joke Version ^2.0 | — | — |
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
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.