The project has had no release or commit activity for about four years, and its repository has no security policy. It is clearly packaged with documentation, tests in the repository, a changelog, and a matching source repository, but the license texts do not fully agree and workflow actions are unpinned.
55%
Total Score
25
70
75
The package has only two releases, with the latest on April 13, 2022 and none in the last 12 months; this materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating inactive maintenance.
The release declares GPL-3.0-or-later and LGPL-3.0-or-later and includes a license file, but the detected text includes LGPL-3.0 and MIT, creating a licensing discrepancy that should be clarified.
The package and repository are owned by the same individual account rather than an organization, so the single registry maintainer represents a thin backing structure alongside the inactivity evidence.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a package that generates regulatory files.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
thecodingmachine/safe Version ^1.3.3 | — | — |
nfephp-org/sped-common Version ^5.0.57 | — | — |
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.