The package has a very small footprint and no automated security tooling. Recent releases are encouraging, but the repository has had no commits or issue activity in the last three months, leaving long-term maintenance uncertain.
58%
Total Score
50
81
83
A README is present, but it is only 24 characters and provides very little integration guidance. Missing tests and changelog files are normal for a published artifact and are not counted as gaps here.
The repository had 0 commits and 0 active maintainers in the last 3 months. Although the recent release is positive, the lack of observed development activity raises maintenance risk.
There were no new or closed issues or pull requests in the last month. With no other evidence of active collaboration, this suggests limited project activity.
The repository name does not match the package name and its README does not mention the package. That creates some uncertainty about the repository-to-package relationship, although the file tree is consistent with a small library.
Composer is used for the build, but no security scanning tools are present. This is a hygiene gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ibazhe/cookies Version ^1.1.8 | — | — |
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.