Detect if we were run as a result of `npm publish`. For more information about this package, visit its homepage.
The npm package in-publish 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.
The npm package in-publish ranks among the top 10000 projects in this community. It has 411M 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.
Since we can't know when or where malicious attacks will happen, we recommend tracking how in-publish behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a in-publish version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.
... 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.