Was css-to-js-sourcemap-worker Hacked?

No Publicly Reported Incidents. As of July 2026, css-to-js-sourcemap-worker has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates css-to-js-sourcemap-worker's security posture as strong (security dimension score: 90/100). Trust Score: 48/100 (D). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score48/100 (D)
Security Dimension90/100
Publisherrtsao
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see css-to-js-sourcemap-worker Trust Score on Nerq.

FAQ

Has css-to-js-sourcemap-worker been hacked?
As of July 2026, css-to-js-sourcemap-worker has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does css-to-js-sourcemap-worker have?
css-to-js-sourcemap-worker has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is css-to-js-sourcemap-worker safe to use after a breach?
With no reported breaches, css-to-js-sourcemap-worker appears safe based on available data.
Where can I check css-to-js-sourcemap-worker's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for css-to-js-sourcemap-worker. View the full trust analysis at nerq.ai/safe/css-to-js-sourcemap-worker.

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy