PHP strip_tags in Node.js
62%
Total Score
50
100
90
50
50
No build attestation or trusted-publisher provenance is present, reducing publication transparency. This is a moderate hygiene gap rather than evidence that the release is unsafe.
Only one registry publishing maintainer is listed, which creates a thin publishing base and some continuity risk. The repository's established history partly compensates, but no additional active publisher is shown.
The package has 20 releases since 2014, but its latest release was nearly four years ago and there were no releases in the last 12 months. This materially raises abandonment and stale-maintenance risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The non-archived status provides some context but does not offset the lack of recent activity.
The sole workflow was fully analyzed with no injection or high-severity findings, but both of its two action references are unpinned. That leaves avoidable build reproducibility and action-update risk.
| Title | Versions | Severity |
|---|---|---|
CVE-2021-32696 striptags is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in versions 0.0.0 - 3.2.0. | 0.0.0 - 3.2.0 | Low |
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.