@4c/layoutv2.0.5

Copy SHA256

License: Permissive (MIT)

npm

Homepage

Published:

Warning

Risk: Vulnerabilities

1 medium severity vulnerabilities

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 medium severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Issues

See all issues

medium

Detected presence of medium severity vulnerabilities.

vulnerabilities

Behaviors

No behaviors found

Vulnerabilities

Downloads

205.71K

Recorded Downloads Since 2021

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for @4c/layout

What is @4c/layout?

For more information about this package, visit its homepage.

Is @4c/layout malicious or is it safe to use?

The npm package @4c/layout 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 @4c/layout popular?

The npm package @4c/layout is not widely used. It has 206K 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 @4c/layout once it is in my app?

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