Spectra Assure
Community
passEverything is awesome!
Scanned: 4 days ago

@npmcli/redact

latest
Redact sensitive npm information from output
License: Permissive (ISC)
Published: 3 months ago
Visit GitHub
See on npm

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

327.09M
Recorded Downloads Since 2021
8
Contributors
0
Declared Dependencies
9
Dependents

Top issues

See all issues

Problem

Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.

Prevalence in npm community

3 packages
found in
Top 100
25 packages
found in
Top 1k
322 packages
found in
Top 10k
64.27k packages
in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.
If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

Top behaviors

See all behaviors

Prevalence in npm community

Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
2 packages
found in
Top 100
17 packages
found in
Top 1k
210 packages
found in
Top 10k
47.61k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
32 packages
found in
Top 100
170 packages
found in
Top 1k
1960 packages
found in
Top 10k
553.47k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
38 packages
found in
Top 100
214 packages
found in
Top 1k
2284 packages
found in
Top 10k
625.04k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
72 packages
found in
Top 100
465 packages
found in
Top 1k
5356 packages
found in
Top 10k
1.75M packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for @npmcli/redact

What is @npmcli/redact?

Redact sensitive npm information from output. For more information about this package, visit its homepage.

Is @npmcli/redact malicious or is it safe to use?

The npm package @npmcli/redact was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is @npmcli/redact popular?

The npm package @npmcli/redact is not widely used. It has 327M 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 @npmcli/redact once it is in my app?

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

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.