A complete test suite, clear README, MIT licensing, and organization backing support adoption. The CI workflow uses broad write permissions and four unpinned actions, while the repository has no security policy or scanning setup.
61%
Total Score
75
83
50
The package has one release, 1.0.0, published about 8 months ago, with no subsequent releases. That is limited evidence of an established maintenance cadence and lowers confidence in continued support.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, and its latest push was on the release date. This indicates no observed ongoing development.
The repository has no security policy and no policy file was detected. This is a transparency and maintenance gap, although it is less serious than evidence of unsafe release behavior.
All 4 analyzed action references are unpinned and the single workflow grants top-level write permissions, creating modest reproducibility and token-scope concerns. No untrusted checkout, script injection, dangerous trigger, or auditor finding was detected, so this is not a severe workflow risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^6.4.15 || ^7.0 | — | — |
symfony/config Version ^6.4.15 || ^7.0 | — | — |
symfony/framework-bundle Version ^6.4.15 || ^7.0 | — | — |
symfony/dependency-injection Version ^6.4.15 || ^7.0 | — | — |
aeatech/transaction-manager-core Version ^1.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.