Loading the registry…
Encryption, hashing, and blind indexing for Pydantic
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
This artifact ships from 3 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/julien777z/pydantic-encryption, 136 findings
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- pydantic_encryption
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
6 findings · 0.6s
v2.0.11
94 findings · 8.4s
v0.3.74
30 findings · 4.2s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v0.1.0
2 findings · 10.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 132 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 127 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-001 · Files: AGENTS.md · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 HIDDEN_DATA_FILE
Files: /repo/.agents/skills/security-audit/render-artifacts.cjs, /repo/.agents/skills/security-audit/validate-findings.cjs · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
64 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: HIDDEN_DATA_FILE, agents-no-model-agents/code-simplify.md, MANIFEST_MISSING_LICENSE · Files: /repo/.agents/rules/github.md, /repo/.agents/rules/project.md, /repo/.agents/skills/code-simplify/SKILL.md and 45 more · reported by cisco-skill-scanner, agentshield
63 The review call did not complete.
Rules: AAK-SECRET-004, DATA_EXFIL_JS_FS_ACCESS, AAK-AGENT-003 and 13 more · Files: tests/unit/test_config.py, tests/unit/test_sqlalchemy/test_bulk.py, /repo/.agents/skills/security-audit/render-artifacts.cjs and 24 more · reported by agent-audit-kit, cisco-skill-scanner, agentshield and 1 more
Critical findings, potential credential exposure, and shell execution.
Critical findings are present in `pydantic_encryption` components related to `sqlalchemy` integration and lazy loading. Potential credential exposure is identified in `gauntlet.py` and `aws.py`. Additionally, shell script execution capabilities are present in `hooks/simplify-on-stop.sh`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 19 of 19; the rest are in the per-scanner reports above.