safe-evalv0.4.1

latest

Copy SHA256

License: Permissive (MIT)

npm

Homepage

Published:

Safer version of eval()

Fail

Risk: Vulnerabilities

4 severe vulnerabilities exploited

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

4 severe vulnerabilities exploited

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Downloads

5.59M

Recorded Downloads Since 2021

Maintenance

Maintainer

Dependencies

Declared Dependencies

Dependents

288

Dependents

Issues per Version Graph

Scanned

FAQ for safe-eval

What is safe-eval?

Safer version of eval(). For more information about this package, visit its homepage.

Is safe-eval malicious or is it safe to use?

The npm package safe-eval was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is safe-eval popular?

The npm package safe-eval is not widely used. It has 6M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure safe-eval once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how safe-eval behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a safe-eval version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.