by
SPINX Digital
0 (0 reviews)
SRI Shield
Add Subresource Integrity hashes to enqueued scripts and styles, approve changed files before they are trusted, and scan pages for missing SRI.
SRI Shield ranks #66,764 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.2.0
Current Version v1.2.0
Updated 3 days ago
Last Update on 29 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#3,855 of 5,058 in Security
Actively maintained
Rank
#66,764
—
No change
Active Installs
0+
—
No change
KW Avg Position
31.7
—
No change
Downloads
30
+44 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
39,196
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#66,764
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.2.0
- Last Updated
- Oct 29, 2026
- Requires WP
- 7.0+
- Tested Up To
- 7.1.4
- PHP Version
- 8.0 or higher
- Author
- SPINX Digital
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about SRI Shield
It is a browser security feature. Each script or stylesheet tag carries a hash of the file's expected content. Before using the file, the browser checks that its content still matches the hash, and blocks it if it does not.
No. SRI confirms that a file matches a hash; it does not decide whether the file is trustworthy. SRI Shield trusts each file's content the first time it is hashed and asks you to approve every later change. Review changes before approving them, and keep using your other security measures.
No. Every feature is available through settings screens in your WordPress dashboard, and the plugin works with safe defaults.
CSS and JavaScript assets that are enqueued through WordPress, whether they are local, on a CDN, or on another remote service. Scripts and stylesheets added to pages in other ways (hard-coded tags or JavaScript injection) are not given integrity attributes.
No. The scanner analyzes the HTML your server returns and does not run JavaScript, so assets injected at runtime are not detected.
Yes. SRI Shield can hash remote assets via secure HTTP requests when the URL is accessible from your server. If a file cannot be reached or verified, it is left without an integrity attribute rather than causing an error. Cross-origin SRI also requires the CDN to send CORS headers.
Only when the Process Admin Assets setting is enabled. It is off by default.
Not while files are unchanged. If a protected file changes and the change has not been approved yet, browsers refuse that file, which can affect the features that depend on it until you review the change.
Hashes are stored and reused, so files are not re-hashed on every visit. A local file is hashed again only when its modification time or size changes.
SHA-384. It is strong, widely supported, and the default. SHA-256 and SHA-512 are also available if you have a specific reason to change it.
