The first release is too new to demonstrate a maintenance track record. Clear documentation, tests, release notes, and a matching repository help, but the missing security policy leaves transparency incomplete.
68%
Total Score
83
100
88
83
A single registry maintainer is consistent with a user-owned project, but it leaves limited visible publishing redundancy. The repository's direct name match and documentation support genuine ownership.
This is the package's first release, published today, so there is no release history or cadence demonstrating sustained maintenance. The repository's tests and release notes provide some compensating evidence, but not a track record.
Composer is used as the build tool, but no security scanning tools are reported. For a package that handles shipping-provider integration, this is a modest transparency and maintenance gap.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
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.