The small dependency set, MIT declaration, matching repository, and clear README support straightforward use. The project has not committed or released for about nine months after publishing five versions on one day, while lacking a security policy.
58%
Total Score
50
100
86
83
The repository is owned by an individual user rather than an organization, so the small visible project footprint provides limited evidence of ongoing backing.
All five releases were published within one day, and the latest release was about nine months ago. This suggests an initially rushed release burst followed by a long maintenance gap.
There were no commits and no active maintainers in the last three months, reinforcing the broader concern that development has stalled.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest repository-hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting expectations unclear for a transaction-management library.
We didn't find any vulnerabilities for this package.
No maintainer information available.
No direct dependencies.
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.