Caveat verdict

blogger-auto-publish

blogger-auto-publish-clean

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Google Blogger publishing automation using the official OAuth2/Blogger API v3; credential_access reads the user own Google credentials and token.json to post to the user own blog, which is the documented intended purpose.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

28
security
50
transparency
80
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (4)

Pattern match high

Accesses shell history/config

INSTALL.md · code · ~/.zshrc

Pattern match high

Recursive delete from root or home — destructive command

INSTALL.md · prose · downgraded · rm -rf ~

Confirmed in code medium

Accesses process.env — reads environment variables

SKILL.md · code

Pattern match low

References webhook/callback URL

assets/template-config.js · prose · downgraded · webhookUrl

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

package_installcredential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API