The package has clear usage documentation, a stable version, and a small runtime dependency surface. Its source has had no commits or releases for more than three years, while one registry maintainer and no security scanning increase maintenance risk.
42%
Total Score
25
100
75
50
The package has had no releases in the last 12 months, and its latest release was more than three years ago. The five-release history shows an initially active project but does not compensate for the prolonged pause.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the latest push being more than three years ago. This is strong evidence of abandonment risk.
Only one account has registry publish access. That can be normal for a small package, but with no recent repository activity it leaves little visible maintenance capacity.
The repository uses Composer, which fits the package ecosystem, but it has no security scanning tools. That is a hygiene gap, though it is less serious than the lack of maintenance activity.
The repository has no security policy. For a package integrating with a boleto API, this reduces transparency around vulnerability reporting, with no provided compensating security process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5.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.