SECURITY REPORT · EXTENSHI SCAN
MockFill: API Mocking
Chrome extension·by Shadab
62
/ 100 SAFETY SCORE
RISKY
Several elevated signals. Read the findings before sharing this with your team.
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
MockFill: API Mocking's safety score vs every other extension we've scanned
Globally
61.5%of extensions carry more risk
Riskier ←→ Safer
Ranked across every extension we scan
In its category
51.5%of its category extensions carry more risk
Riskier ←→ Safer
Ranked within its category
Findings
20
median 38Lower is safer
Risky permissions
0
median 1Critical + high perms
Total permissions
1
median 4All declared perms
Critical findings
2
median 2Severity = Critical
Findings breakdown
Automated security signal · 20 distinct issues across 6 severities
20
distinct issues
detected
detected
Scanners reported 25 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical210%
High630%
Needs Review00%
Medium840%
Low420%
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 MockFill: API Mocking?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show MockFill: API Mocking's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 11, 2026· partial run (some scanners failed)
Browser extensions made transparent.