Dynamically polyfill only when needed by the browser. Complementary to Polyfill.io
48%
Total Score
33
100
75
75
50
The latest release was in March 2018, with no releases in the last 12 months as of collection in September 2026. This long publishing gap is a substantial abandonment concern, despite six historical releases and a previously regular cadence.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old last push, this is strong evidence that maintenance has stopped.
No build attestation, trusted publisher identity, or staged publishing is present. This weakens release transparency, although the package's simple artifact and lack of runtime dependencies limit the practical impact.
The repository is owned by an individual user rather than an organization, so there is no organizational backing visible to compensate for the single-maintainer publishing setup or stalled activity.
There were four open issues and no new or closed issues, pull requests, or merges during the last month. This indicates no visible recent triage or development activity.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2024-10148 dynamic-polyfill is vulnerable to Malicious Code in all versions. | 0.0.0 - * | Critical |
No direct dependencies.
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.