SECURITY REPORT · EXTENSHI SCAN
budget process : 30/30/30 rule
Chrome extension·by simozin
0
/ 100 SAFETY SCORE
EXCELLENT
Looks clean. No meaningful risks detected in this scan.
Automated analysis of publicly available code — not a professional security audit. It may produce false positives and does not prove an extension is unsafe or safe. Treat it as one signal among many. Disclaimer · Report an issue
How it ranks
budget process : 30/30/30 rule's safety score vs every other extension we've scanned
Globally
53%of extensions carry more risk
Riskier ←→ Safer
Ranked against 369,936 extensions
In Productivity
67%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,133 productivity extensions
Findings
11
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
1
median 3Declared in manifest
Active users
11
median 14vs category median
Findings breakdown
Automated security signal · 11 distinct issues across 6 severities
11
distinct issues
detected
detected
Critical00%
High00%
Needs Review00%
Medium11100%
Low00%
Info00%
Permissions requested
1 permission declared
No risky permissions
1 permission requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Are you the author of budget process : 30/30/30 rule?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show budget process : 30/30/30 rule's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 10, 2026
Browser extensions made transparent.