📦

Audit History

changelog-automation - 9 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v9 LatestJul 7, 2026, 06:43 AM No confirmed findings0No capability change
v8 Jul 7, 2026, 06:43 AM No confirmed findings0No capability change
v7 Jun 30, 2026, 10:19 PM No confirmed findings2No capability change
v6 Jun 30, 2026, 10:19 PM No confirmed findings2External commandsNetwork accessEnv variables
v5 Jan 21, 2026, 06:55 PM No confirmed findings0 Network accessExternal commandsEnv variables
v4 Jan 17, 2026, 07:47 AM No confirmed findings0No capability change
v3 Jan 17, 2026, 07:47 AM No confirmed findings0Network accessExternal commandsEnv variables
v2 Jan 4, 2026, 04:51 PM No confirmed findings0No capability change
v1 Jan 4, 2026, 04:51 PM No confirmed findings0Baseline

Jun 30, 2026, 10:19 PM

Static analysis flagged many command, network, token, and weak-crypto patterns. Review found no malicious code or prompt injection; most flags are documentation examples, Markdown fences, URLs, and false positives from words such as description. The skill is publishable with warnings because it teaches release workflows that can push tags, create releases, and use GitHub or npm tokens.

1
Files scanned
553
Lines analyzed
5
Review items
2
False positives ignored
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
Release Automation Examples Use Write Tokens
The workflow example grants repository write permissions and uses GitHub and npm tokens. This is legitimate release automation, but copying it without review can publish packages or push release changes.
The lines clearly show write permissions and token-backed release steps. The context is instructional, so the risk is operational rather than malicious.
Medium
Examples Include Commands That Modify Project State
The skill provides commands for installing tools, writing configuration, bumping versions, generating changelogs, and pushing tags. These commands are expected for the skill, but should not be run without user confirmation.
The commands are visible in fenced examples and directly affect repository files or release state. They appear legitimate for changelog automation.
Static false positives ignored (2)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Hardcoded URLs Are Documentation References
The detected URLs point to standards, example GitHub compare links, and project resources. No evidence found that the skill sends data to these URLs.
The URLs are Markdown links or template examples, not executable network calls. Their context matches public changelog documentation.
Low
Weak Cryptography Alerts Are False Positives
The scanner flagged text such as description and changelog-related examples. No evidence found of cryptographic APIs, hashing code, or security-sensitive algorithm selection.
The flagged lines are prose, placeholders, or configuration values. They do not implement encryption, hashing, or authentication logic.
Audited by: codex

Jun 30, 2026, 10:19 PM

Static analysis flagged many command, network, token, and weak-crypto patterns. Review found no malicious code or prompt injection; most flags are documentation examples, Markdown fences, URLs, and false positives from words such as description. The skill is publishable with warnings because it teaches release workflows that can push tags, create releases, and use GitHub or npm tokens.

1
Files scanned
553
Lines analyzed
5
Review items
2
False positives ignored
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
Release Automation Examples Use Write Tokens
The workflow example grants repository write permissions and uses GitHub and npm tokens. This is legitimate release automation, but copying it without review can publish packages or push release changes.
The lines clearly show write permissions and token-backed release steps. The context is instructional, so the risk is operational rather than malicious.
Medium
Examples Include Commands That Modify Project State
The skill provides commands for installing tools, writing configuration, bumping versions, generating changelogs, and pushing tags. These commands are expected for the skill, but should not be run without user confirmation.
The commands are visible in fenced examples and directly affect repository files or release state. They appear legitimate for changelog automation.
Static false positives ignored (2)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Hardcoded URLs Are Documentation References
The detected URLs point to standards, example GitHub compare links, and project resources. No evidence found that the skill sends data to these URLs.
The URLs are Markdown links or template examples, not executable network calls. Their context matches public changelog documentation.
Low
Weak Cryptography Alerts Are False Positives
The scanner flagged text such as description and changelog-related examples. No evidence found of cryptographic APIs, hashing code, or security-sensitive algorithm selection.
The flagged lines are prose, placeholders, or configuration values. They do not implement encryption, hashing, or authentication logic.
Audited by: codex

Jan 21, 2026, 06:55 PM

This skill contains documentation and configuration templates for changelog automation tools. All static findings are false positives: network URLs are documentation references to keepachangelog.com and semver.org, backtick patterns are code examples in markdown format, and env_access references are configuration samples for GitHub Actions workflows. No executable code or security risks detected.

2
Files scanned
1,378
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude

Jan 4, 2026, 04:51 PM

Pure documentation skill containing only markdown templates and configuration examples. No executable code, no file access, no network calls, no command execution. The skill provides patterns that users apply manually to their own projects.

4
Files scanned
1,108
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude

Jan 4, 2026, 04:51 PM

Pure documentation skill containing only markdown templates and configuration examples. No executable code, no file access, no network calls, no command execution. The skill provides patterns that users apply manually to their own projects.

4
Files scanned
1,108
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude