PHP classes to work with the Cyberpunk 2077 DB.
63%
Total Score
caution
No releases or commits have appeared for about 17 months, despite a complete, tested package and a non-archived repository.
The repository is owned by a user account rather than an organization, so the project appears to rely on individual ownership. This matters alongside the single registry maintainer and absent recent activity.
The package has had 14 releases, but none in the last 12 months; the latest release was about 17 months ago. This indicates materially slowed maintenance despite a previously regular release cadence.
There were no commits and no active maintainers in the last three months. Combined with the long release gap, this is the clearest abandonment concern.
Composer build tooling is present, supporting reproducible package work, but no security scanning tools were detected. The missing scanning is a modest maintenance and supply-chain hygiene gap.
The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
brick/event Version >=0.1.1 | — | — |
loupe/loupe Version >=0.7.0 | — | — |
mistralys/changelog-parser Version >=1.0.2 | — | — |
mistralys/cyberpunk-mod-db Version >=2.3.0 | — | — |
mistralys/application-utils-core Version >=2.3.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.