Payments for vivutio: what the organization is owed for its bookings and tickets, gathered from every module, and the payments received against it, recorded by hand.
62%
Total Score
caution
A brand-new package has no demonstrated maintenance history and an unpinned, potentially unsafe release workflow.
The package declares 19 runtime dependencies, including framework and application components. That is a meaningful integration surface, but the signal does not show an inherently unsafe or excessive dependency pattern.
The package is effectively brand new: it has two releases and was published only hours ago, with the latest release about 37 minutes after the first. This provides too little history to establish dependable maintenance.
There were no commits or active maintainers in the last three months. Because the project was published only hours ago, this is partly explained by its age, but it still leaves ongoing maintenance unproven.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and hygiene gap, not evidence of abandonment by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/clock Version ^1.0 | — | — |
twig/twig Version ^3.21 | — | — |
symfony/uid Version ^8.0 | — | — |
doctrine/orm Version ^3.5 | — | — |
symfony/clock Version ^8.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.