-
Notifications
You must be signed in to change notification settings - Fork 14
Add documentation for Malware Scanning feature #386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,17 @@ | ||||||
| --- | ||||||
| title: Malware Scanning | ||||||
| --- | ||||||
|
|
||||||
| # Malware Scanning | ||||||
|
|
||||||
| Malware Scanning automatically checks packages for known malicious content — such as trojans, viruses, and other malware — as they are uploaded to your Cloudsmith repository. It is powered by [ClamAV](https://github.com/Cisco-Talos/clamav) and runs on every uploaded package before it becomes available for download. | ||||||
|
|
||||||
| If a threat is detected, the package upload fails at sync with a reason of "malware detected" and the package is not made available in the repository. | ||||||
|
|
||||||
| If you feel a package has been incorrectly identified as containing malware, please [contact us](https://cloudsmith.com/company/contact-us). | ||||||
|
|
||||||
| ## Malware Scanning vs. Enterprise Policy Management | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just policy management throughout, not Enterprise Policy Management |
||||||
|
|
||||||
| Enterprise Policy Management and the detection of malicious and vulnerable packages are based on security feeds and match to packages pulled from Upstream sources; like, NPMJS, Maven Central, etc. | ||||||
|
||||||
| Enterprise Policy Management and the detection of malicious and vulnerable packages are based on security feeds and match to packages pulled from Upstream sources; like, NPMJS, Maven Central, etc. | |
| Enterprise Policy Management and the detection of malicious and vulnerable packages are based on security feeds and match to packages pulled from Upstream sources such as NPMJS, Maven Central, etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably not capitalise Upstream here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like the match to packages reads funny. The way we've lumped policy management with the detection and then referring to matching there.
Copilot
AI
Apr 8, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spelling error: "Securit" should be "Security"
| EPM is available to customers with our Advanced Securit add-on. | |
| EPM is available to customers with our Advanced Security add-on. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it's a named feature like that. Policy Management is available to customers with our advanced security capabilities. maybe instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would probably remove your/you where we've referenced them