Skillrx— plugin

Skillrx — independently scanned and version-tracked by SaferSkills.

by felipeinf·Plugin·github.com/felipeinf/skillRx

Is Skillrx safe to install?

SaferSkills independently audited Skillrx (Plugin) and scored it 15/100 (red). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 2 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
15/100
●●○○○○○○○○
↑ +0 since first scan (15 → 15)Re-scan~30s
Latest scan
ScannedJun 24, 2026 · 29d ago
Scans run2 over 90 days
Detectors55 checks · 5 categories
Findings0 warnings · 2 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
20
7.0 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 2 flagged

Securityscore 20 · 2 findings
CRITICALReads your AWS credentials fileSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01 · Credential exfiltration · src/analyzers/secretsAndCreds.js×2
CRITICALfull cloud credentials are tier-1 exfiltration material — a read here can mean total account takeover.
Why it matters

This plugin references the AWS credentials file or the access-key fields stored inside it (re: /AWS_SECRET_ACCESS_KEY\s*=\s*['"]?([A-Za-z0-…). Those are long-lived keys with broad cloud access, so any code that reads them can hand your whole AWS account to whatever it contacts next.

The exact value spotted
excerptsrc/analyzers/secretsAndCreds.js· javascript
25rule: "aws-secret",
26severity: "high",
27re: /AWS_SECRET_ACCESS_KEY\s*=\s*['"]?([A-Za-z0-9/+=]{40})/gi,
28},
29{
Occurrences
2 occurrences · first at L27, also L32
Show all 2 locations
Line
File
L27
src/analyzers/secretsAndCreds.js
L32
src/analyzers/secretsAndCreds.js
How to fix
Remove the direct read of ~/.aws/credentials; let the AWS SDK resolve credentials through its standard provider chain instead.
  1. Delete code that opens or parses the credentials file or its key fields by hand.
  2. Use the SDK's default credential resolution so secrets never pass through plugin code or leave the machine.
Avoidcreds = open(os.path.expanduser("~/.aws/credentials")).read() requests.post(url, data={"creds": creds})
Safer pattern# let the SDK resolve credentials; never read or transmit the file yourself import boto3 s3 = boto3.client("s3")
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01sha256f45f1bce16d0761erubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.