Security Audit

azure-mgmt-applicationinsights-dotnet

github.com/sickn33/antigravity-awesome-skills

AI SkillCommit e36d6fd3b3f6

TRUSTED

Scanned about 5 hours ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

azure-mgmt-applicationinsights-dotnet received a trust score of 85/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.

SkillShield's automated analysis identified 2 findings: 0 critical, 0 high, 1 medium, and 1 low severity. Key findings include Unpinned dependencies in installation instructions, Example code prints sensitive credentials to console.

The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.

Last analyzed on February 20, 2026 (commit e36d6fd3). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

91%

Behavioral Risk Signals

Shell Execution

2 findings

Security Findings2

Severity	Finding	Layer	Location
MEDIUM	Unpinned dependencies in installation instructions The `dotnet add package` commands in the installation section do not specify a version. This can lead to non-deterministic builds and potentially pull in vulnerable or incompatible package versions if a malicious update or breaking change is introduced in a future release. It is a best practice to pin dependencies to specific versions or at least major versions to ensure stability and security. Specify exact or major versions for NuGet packages in the installation commands. For example, use `dotnet add package Azure.ResourceManager.ApplicationInsights --version 1.0.0` or `dotnet add package Azure.ResourceManager.ApplicationInsights --version 1.*`.	LLM	SKILL.md:11
LOW	Example code prints sensitive credentials to console The skill's example code demonstrates retrieving and printing sensitive credentials such as `InstrumentationKey`, `ConnectionString`, and `API Key` directly to the console. While this is common in documentation for user visibility, in an automated agent context, executing such code could lead to these credentials being logged or exposed if the agent's output is not securely handled. The comment `// Only shown once!` for the API key highlights its sensitivity. Advise users/agents to store and handle these credentials securely (e.g., Azure Key Vault, environment variables, secure configuration management) rather than printing them to standard output. For documentation, consider replacing direct printing with a note about secure storage and retrieval.	LLM	SKILL.md:78

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/2cde3a5365a2d7bc.svg)](https://skillshield.io/report/2cde3a5365a2d7bc)