Afosto PostNL ECS Client
38%
Total Score
unhealthy
Risky: no release or repository activity since June 2017 signals a strong abandonment risk.
The latest release was in June 2017, with no releases in the last 12 months despite a 15-release history. A long period without updates materially raises abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having been inactive since June 2017. This is strong evidence of absent ongoing maintenance.
There were no new or closed issues or pull requests in the last month, and no open work is visible. This supports the conclusion that the project is not actively maintained, though a quiet package can have no support demand.
The repository has zero stars, forks, and watchers, providing no community adoption or backup-maintainer evidence. Popularity is only supporting evidence, so this reinforces rather than establishes the maintenance concern.
The repository has no security policy and no security scanning tools. For a package handling PostNL integration data, this weakens transparency and vulnerability-response readiness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
afosto/bp Version ^2.0.0 | — | — |
sabre/xml Version ^1.5 | — | — |
league/flysystem Version ^1.0 | — | — |
league/flysystem-sftp Version ^1.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.