Usable with caveats: it is actively released and backed by an organization, but the repository appears to contain no concrete package code and all recent commits come from one contributor. The missing security policy and minimal repository activity make this a less transparent dependency than its release cadence suggests.
62%
Total Score
83
88
50
A README is present, but it explicitly says the repository provides no concrete code to document; tests and a changelog are absent. Missing tests and changelog are not concerns for the published artifact by themselves, but the README's description of an apparently empty package is a transparency concern.
One contributor made all 14 commits in the last 3 months, creating a meaningful continuity risk if that person stops maintaining the package. Organization backing provides some capacity to hand maintenance off, but no second active contributor is shown.
Composer build tooling is present, which fits the package ecosystem, but no security-scanning tooling was detected. This reduces assurance around ongoing project hygiene.
The repository has no security policy. That is a transparency and vulnerability-reporting gap, although it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
wexample/symfony-money Version >=4.0.0 | — | — |
wexample/symfony-helpers Version >=8.0.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.