What happens to a subject — a user, an organization — kept as a history, recorded by category, each category enabled, kept and purged as the application decides
70%
Total Score
caution
Only two releases and no observed commit activity make long-term maintenance unproven.
The package is brand new, with two releases in less than one day and no established release track record. This limits evidence of sustained maintenance, although the recent second release shows active initial publishing.
There were zero commits and zero active maintainers during the last three months. Because the package is less than one day old, this is mainly a lack of historical evidence rather than proof of abandonment, but sustained maintenance remains unproven.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and hygiene gap, not a standalone supply-chain failure.
The repository has no security policy. This weakens disclosure transparency for a package handling application activity data, though it does not by itself show unsafe code or abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/uid Version ^7.4 || ^8.0 | — | — |
doctrine/orm Version ^3.0 | — | — |
symfony/console Version ^7.4 || ^8.0 | — | — |
symfony/routing Version ^7.4 || ^8.0 | — | — |
symfony/http-kernel Version ^7.4 || ^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.