Clear licensing, tests, and a stable 1.0.0 release provide useful context. The repository is small, has no security policy, and its workflow references are not pinned.
55%
Total Score
75
78
75
The package has only one release, published about 4 years and 1 month ago, with no releases in the last 12 months. This is substantial evidence of low maintenance activity.
The repository recorded no commits and no active maintainers in the last 3 months. Combined with the old release history, this increases abandonment risk.
The repository name does not match the package name and its README does not mention the package, so the repository may not clearly correspond to this release. Organizational backing and the matching source structure partly reduce this concern.
The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but it offers little external evidence of active use.
The project uses Composer and Make, but no security scanning tools were detected. This is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/api Version ^0.1.0 || ^0.2.0 || ^0.3.0 | — | — |
spryker/log Version ^1.0.0 || ^2.0.0 || ^3.0.0 | — | — |
spryker/api-query-builder Version ^0.1.0 | — | — |
fond-of-spryker/shipment-delivery-note Version * | — | — |
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.