Classe d'utilisation des API de consultation d'Apidae
66%
Total Score
caution
Usable with caveats: unclear repository ownership and no recent commits weaken maintenance confidence.
There were zero commits and zero active maintainers in the last three months. This conflicts with the recent registry release and leaves current development activity uncertain.
The repository name does not match the package name and its README does not mention the package. That makes the repository-to-package relationship less clear, despite the repository being linked directly.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little independent evidence of community adoption.
Composer is used as the build tool, but no security-scanning tools were detected. The missing scanning tooling is a modest hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. That weakens vulnerability-reporting transparency, though it does not by itself show abandonment or make the release unfit.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
guzzlehttp/uri-template Version ^0.2.0 | — | — |
pierre-granger/apidae-core Version ^0.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.