Is secret-serialization safe?
Grade A, 100/100. No meaningful risk found.
Finds secrets, tokens, passwords, and API keys that can leak through generated serialization: Python dataclass repr and asdict, attrs, pydantic model_dump, NamedTuple, JavaScript JSON.stringify and util.inspect, structured logs, tracing spans, and error reports. Use when asked to "check for secret serialization", "credential in repr", "repr=False audit", "secret in spans", "token in logs", or when a change adds a credential field to a dataclass, model, or config object, or adds code that stringifies whole objects or every kwarg into telemetry.
Asecret-serialization
skills/secret-serialization100/100 · No meaningful risk foundNo security findings
secret-serialization
skills/secret-serializationFinds secrets, tokens, passwords, and API keys that can leak through generated serialization: Python dataclass repr and asdict, attrs, pydantic model_dump, NamedTuple, JavaScript JSON.stringify and util.inspect, structured logs, tracing spans, and error reports. Use when asked to "check for secret serialization", "credential in repr", "repr=False audit", "secret in spans", "token in logs", or when a change adds a credential field to a dataclass, model, or config object, or adds code that stringifies whole objects or every kwarg into telemetry.
- Content hash
- sha256:0e99c113dccde98961cebd4d4b2c4db3a5f5d069edc508519d44dbd3d14b2456
- Files
- 5
- Quality
- 100/100
Security findings
None of the 30 rules matched.
Files in this skill
- SKILL.md10.2 KB
- SOURCES.md6.8 KB
- SPEC.md5.1 KB
- references/javascript-typescript.md5.1 KB
- references/python.md9.9 KB
Questions about secret-serialization
- Is secret-serialization safe to install?
- Our scanner gave secret-serialization grade A (100/100): no meaningful risk found. None of the 30 security rules matched. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
- How do I install secret-serialization in Claude Code or Codex?
- Run skillhash add github:getsentry/skills/skills/secret-serialization. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
- What happens if secret-serialization changes upstream?
- Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.
More from getsentry/skills
- A
agents-md
1.1kgetsentry/skills
Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.
No security findings - A
blog-writing-guide
1.1kgetsentry/skills
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
No security findings - A
brand-guidelines
1.1kgetsentry/skills
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
No security findings - A
claude-settings-audit
1.1kgetsentry/skills
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
No security findings - A
code-review
1.1kgetsentry/skills
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
No security findings - A
code-simplifier
1.1kgetsentry/skills
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
No security findings - A
commit
1.1kgetsentry/skills
Use for every request to commit changes or draft a commit message. Creates Sentry-style conventional commits with issue references.
No security findings - A
create-branch
1.1kgetsentry/skills
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
No security findings