Chronopost Api usage with php
61%
Total Score
50
50
83
50
Ten runtime dependencies, including several related Chronopost packages, increase the dependency surface and coordination burden, though the profile is coherent for a multi-service API client.
Only one registry publishing account is listed, leaving limited visible publishing redundancy. The repository is user-owned rather than organization-owned, so there is no provided evidence of a broader backing team.
The repository is owned by the same individual namespace that publishes the package, providing direct identity alignment but no evidence of organizational backing.
Seven releases were published over the package's 211-day lifetime, but the latest release was about six months before collection, indicating a recent pause after an initially active period.
There were no commits and no active maintainers in the three months before collection, consistent with the release pause and increasing abandonment risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
moneyphp/money Version ~4.6 | — | — |
kwaadpepper/chronopost-relay Version ^2.0 | — | — |
kwaadpepper/chronopost-creneau Version ^2.0 | — | — |
kwaadpepper/chronopost-searchbt Version ^2.0 | — | — |
kwaadpepper/chronopost-shipping Version ^2.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.