nanomdm
Audited by Socket on Mar 11, 2026
1 alert found:
Obfuscated FileThe NanoMDM skill description and usage pattern align reasonably with its stated purpose of guiding the building/operating of NanoMDM-based MDM solutions. The footprint is coherent: it relies on official NanoMDM sources, uses standard container images and Go module dependencies, and describes common authentication and command-flow patterns appropriate for an MDM server. The primary security considerations are credential exposure in documentation (API keys in curl commands), proper handling of certificates and private keys, and ensuring that webhooks/external endpoints are trusted and access-controlled. No evidence suggests arbitrary credential harvesting, data exfiltration, or unverified binary installation from unverifiable sources within the provided material. Overall risk is primarily Moderate (suspicious in places due to credential exposure patterns in docs) with low malware likelihood, but attention to secret handling and endpoint trust is advised.