head to head · open source
trivy vs eNMS
trivy has 37,969 GitHub stars, 692 forks, 269 open issues and last shipped yesterday. eNMS has 842 stars, 160 forks, 29 open issues and last shipped 4 months ago. trivy leads on adoption by 4,409% (37,969 vs 842 stars). trivy is written in Go under Apache-2.0; eNMS is written in Python under GPL-3.0. trivy has attracted 2% as many forks as stars, eNMS 19%. trivy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (infrastructure-as-code), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| trivy | eNMS | |
|---|---|---|
| GitHub stars | ★ 38K | ★ 842 |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | Python |
| Last push | 2026-09-17 | 2026-05-08 |
| Forks | ⑂ 692 | ⑂ 160 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick trivy if
- You weight community size — 38K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick eNMS if
- You want the eNMS feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Python
- You evaluated both and eNMS fits your workflow better
About trivy
Trivy is an open source security scanner written in Go and released under the Apache 2.0 license. It is an Aqua Security open source project, hosted at trivy.dev, and it lives in the cloud native and DevSecOps ecosystem alongside container runtimes, Kubernetes clusters, and infrastructure as code tooling. The design separates two ideas: scanners, which describe the classes of security issue Trivy looks for, and targets, which describe where it looks. The README presents the project as a comprehensive and versatile scanner, and the topic list — containers, devsecops, docker, iac, infrastructure as code, kubernetes…
read the full trivy overview →
About eNMS
eNMS An enterprise grade vendor agnostic network automation platform. Introduction eNMS is a vendor agnostic NMS designed for building workflow based network automation solutions. It encompasses the following aspects of network automation: Configuration Management Service : Backup with Git, change and rollback of configurations. Validation Services : Validate data about the state of a device with Netmiko and NAPALM. Ansible Service : Store and run Ansible playbooks. REST Service : Send REST calls with variable URL and payload. Python Script Service : Any python script can be integrated into the web UI. eNMS will …
More in Infrastructure & Operations
Related comparisons
More Cloud Infrastructure Management projects
Compare either of these against the rest of the Cloud Infrastructure Management field.
Frequently asked questions
Is trivy or eNMS more popular?
trivy has 37,969 GitHub stars and eNMS has 842. trivy has the larger community by that measure.
Are trivy and eNMS free?
Both are open source. trivy is licensed under Apache-2.0 and eNMS under GPL-3.0. Neither carries a licence fee.
What is the difference between trivy and eNMS?
trivy is written in Go and eNMS in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, trivy or eNMS?
Choose trivy if you want the larger community (37,969 stars) or its Apache-2.0 licence terms. Choose eNMS if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.