Polyfills for PHP 5.3 onwards
55%
Total Score
50
90
75
Only one registry account has publish access, leaving little publishing redundancy. This is a resilience concern for a user-owned project, although the source repository and registry namespace identify the same owner.
The latest release was in February 2020, more than six years ago, and there were no releases in the preceding 12 months. This substantially raises abandonment risk despite the package having eight releases overall.
The repository recorded zero commits and zero active maintainers during the measured three-month period, consistent with the long release pause. The repository is not archived, but there is no recent activity showing ongoing maintenance.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though the package's small, inspectable file tree partly limits its practical impact.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/polyfill-apcu Version ~1.14 | — | — |
symfony/polyfill-util Version ~1.14 | — | — |
symfony/polyfill-iconv Version ~1.14 | — | — |
symfony/polyfill-php54 Version ~1.14 | — | — |
symfony/polyfill-php55 Version ~1.14 | — | — |
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.