The repository is small but includes tests, a changelog, a license, and a matching README. A single publisher, no security policy, and no post-release commit activity leave maintenance capacity and security practice unproven.
64%
Total Score
50
88
75
The package and repository are owned by the same individual account, providing clear ownership but no organization backing or broader institutional support.
This is the package's first release, published 0 days ago, so there is no release history from which to judge sustained maintenance. Its freshness is not abandonment evidence by itself, but it limits maturity evidence.
There were no commits or active maintainers in the last 3 months. Because the release is only 0 days old, this is not evidence of abandonment, but it leaves ongoing maintenance unproven.
The repository uses Composer build tooling, but no security scanning tools were detected. That is a modest transparency and security-practice gap for a package handling shipping integrations.
The repository has no security policy, leaving no documented path for reporting vulnerabilities or explaining security handling.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.3.0 | — | — |
justinholtweb/craft-carrier Version ^5.0.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.