nuget-trusted-publishing
What this skill does
Setup NuGet trusted publishing using OIDC in GitHub Actions workflows, replacing long-lived API keys with short-lived tokens for secure publishing to nuget.org.
github/dotnet - Insecure Workflow Template - 5.1k stars
Threat analysis
Skill info
pkg:github/dotnet/skills@6a37d48?skill=nuget-trusted-publishingAssessments (1)
Insecure Workflow Template
Insecure Workflow Template via local-llm-review
references/publish-workflow.md
The workflow template includes a step that uses `NuGet/login@v1` with a secret `secrets.NUGET_USER`, which is a legitimate practice for OIDC-based publishing. However, the `NuGet/login@v1` action is nBadge
Add the Anomity scan badge for nuget-trusted-publishing to your README.
How Anomity governs this at runtime
Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.
Book a 30-minute demo to see your own skill inventory.
Methodology and disputes
Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of nuget-trusted-publishing? Report an issue or request a rescan.
