A clear README, tests, MIT licensing, and a matching source repository make the package understandable and auditable. Its small dependency surface and lack of install scripts reduce adoption friction, but do not offset the long maintenance gap.
42%
Total Score
0
100
72
75
The package has only two releases, both in August 2016, and none in the last 12 months. That long release gap is strong evidence of abandonment risk for a dependency.
There were no commits or active maintainers in the last three months, consistent with the repository's last push occurring in August 2016. This materially increases the risk that defects and compatibility issues will remain unresolved.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide little evidence of broad community adoption.
The project uses Composer and Phing, showing a defined build process, but no security-scanning tooling is present. The tooling evidence is mixed and the missing scanner is a modest hygiene gap.
The repository has no security policy. For a library intended to mitigate HTML and XSS issues, the absence of a documented vulnerability-reporting path reduces transparency.
We didn't find any vulnerabilities for this package.
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.