📦

Audit History

nx-workspace-patterns - 8 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v8 LatestJul 8, 2026, 12:50 PM 1 confirmed0No capability change
v7 Jul 8, 2026, 12:50 PM 1 confirmed0 Env variables
v6 Jul 1, 2026, 01:07 AM No confirmed findings1No capability change
v5 Jul 1, 2026, 01:07 AM No confirmed findings1Env variables
v4 Jan 17, 2026, 08:51 AM No confirmed findings0No capability change
v3 Jan 17, 2026, 08:51 AM No confirmed findings0Network accessExternal commandsFilesystem access
v2 Jan 4, 2026, 04:50 PM No confirmed findings0No capability change
v1 Jan 4, 2026, 04:50 PM No confirmed findings0Baseline

Jul 8, 2026, 12:50 PM

All static findings were adjudicated as false positives because they are Markdown fences, inline examples, TypeScript template literals, documentation links, or normal Nx configuration references. No prompt injection or data exfiltration intent was found. One semantic issue remains: the remote cache guidance shows token fields directly in configuration, which could lead users to commit real secrets.

1
Files scanned
453
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Hardcoded Cache Token Guidance
The remote cache example places accessToken and nxCloudAccessToken placeholders directly in an nx.json style snippet. Users may copy this pattern with real Nx Cloud tokens and commit secrets.
The cited lines show token fields inside a committed configuration example. The values are placeholders, so the risk is guidance-driven rather than active credential exposure.
Audited by: codex

Jul 8, 2026, 12:50 PM

All static findings were adjudicated as false positives because they are Markdown fences, inline examples, TypeScript template literals, documentation links, or normal Nx configuration references. No prompt injection or data exfiltration intent was found. One semantic issue remains: the remote cache guidance shows token fields directly in configuration, which could lead users to commit real secrets.

1
Files scanned
453
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Hardcoded Cache Token Guidance
The remote cache example places accessToken and nxCloudAccessToken placeholders directly in an nx.json style snippet. Users may copy this pattern with real Nx Cloud tokens and commit secrets.
The cited lines show token fields inside a committed configuration example. The values are placeholders, so the risk is guidance-driven rather than active credential exposure.
Audited by: codex

Jul 1, 2026, 01:07 AM

Static analysis flagged 25 command, 3 URL, 4 filesystem, and 2 weak-crypto patterns. AI review found these to be false positives from Markdown examples, Nx configuration, resource links, and unrelated text. One low-risk content issue remains because cache token placeholders may encourage committed secrets.

1
Files scanned
453
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (1)

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

Low
Cache Token Placeholders in Configuration Example
The remote caching example shows accessToken and nxCloudAccessToken placeholder fields in nx.json. This is not malicious, but users may copy real tokens into versioned configuration instead of secret storage.
The cited lines directly show token placeholder fields in a configuration example. Confidence is below very high because no real secret value or exfiltration behavior is present.

Risk Factors

⚙️ External commands (2)
🌐 Network access (1)
📁 Filesystem access (2)
🔑 Env variables (2)
Audited by: codex

Jul 1, 2026, 01:07 AM

Static analysis flagged 25 command, 3 URL, 4 filesystem, and 2 weak-crypto patterns. AI review found these to be false positives from Markdown examples, Nx configuration, resource links, and unrelated text. One low-risk content issue remains because cache token placeholders may encourage committed secrets.

1
Files scanned
453
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (1)

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

Low
Cache Token Placeholders in Configuration Example
The remote caching example shows accessToken and nxCloudAccessToken placeholder fields in nx.json. This is not malicious, but users may copy real tokens into versioned configuration instead of secret storage.
The cited lines directly show token placeholder fields in a configuration example. Confidence is below very high because no real secret value or exfiltration behavior is present.

Risk Factors

⚙️ External commands (2)
🌐 Network access (1)
📁 Filesystem access (2)
🔑 Env variables (2)
Audited by: codex

Jan 17, 2026, 08:51 AM

This skill contains only static documentation and configuration templates for Nx workspaces. All 41 static findings are false positives: network URLs are legitimate metadata/doc links, external commands are example bash commands in documentation code blocks, path traversal sequences are standard relative paths in JSON config examples, and cryptographic alerts are misidentified schema file paths. The skill has no executable code, no file operations, no data handling, and no network access capability.

2
Files scanned
629
Lines analyzed
3
Review items
0
False positives ignored
Audited by: claude

Jan 17, 2026, 08:51 AM

This skill contains only static documentation and configuration templates for Nx workspaces. All 41 static findings are false positives: network URLs are legitimate metadata/doc links, external commands are example bash commands in documentation code blocks, path traversal sequences are standard relative paths in JSON config examples, and cryptographic alerts are misidentified schema file paths. The skill has no executable code, no file operations, no data handling, and no network access capability.

2
Files scanned
629
Lines analyzed
3
Review items
0
False positives ignored
Audited by: claude

Jan 4, 2026, 04:50 PM

This skill contains only static documentation and configuration templates for Nx workspaces. No executable code, network access, file operations, or data handling is present.

4
Files scanned
453
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:50 PM

This skill contains only static documentation and configuration templates for Nx workspaces. No executable code, network access, file operations, or data handling is present.

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