serialize objects to javascript
58%
Total Score
caution
Usable with caveats: releases stopped in 2022 and repository activity has since gone quiet.
The package has 24 releases, but none in the last 12 months and its latest release was in April 2022, indicating several years without a published update.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the concern raised by the absence of recent releases.
No build attestation or trusted-publisher provenance is present, so publication cannot be independently tied to a verified build process.
Only one registry account has publish access, creating a thin publishing base; the repository's user ownership and inactive commit activity provide no visible organizational redundancy.
The repository is owned by an individual user rather than an organization, so there is no observed organizational backing to offset the thin maintainer base.
| Title | Versions | Severity |
|---|---|---|
CVE-2019-16772 serialize-to-js is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in versions 0.0.0 - 3.0.1. | 0.0.0 - 3.0.1 | Low |
CVE-2017-5954 serialize-to-js is vulnerable to Deserialization of Untrusted Data in versions 0.0.0 - 1.0.0. | 0.0.0 - 1.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.