Skip to main content
WP HealthKit

Is Jamie's Front-End Editor for Content Teams Secure?

A

Grade A — Excellent

Low Risk

Jamie's Front-End Editor for Content Teams passes WP HealthKit's 49-layer security audit with flying colours, earning a Grade A with only 15 minor findings.

Grade

A

Findings

15

Critical

0

Standards

100/100

Active Installs

N/A

Last Audited

Today

What We Found

10 unprefixed global functions detectedHIGH
Parameter #3 $deps of function wp_register_script_module expects array<int|string, array{id: string, import?: string}>, array{'@wordpress…'} given.MEDIUM
Missing 'Tested up to' headerMEDIUM
Unprefixed global function: jfect_get_editable_blocks()MEDIUM
Unprefixed global function: jfect_get_restricted_roles()MEDIUM

+ 10 more findings in the full report.

View Full Report Audit Your Own Plugin

Frequently Asked Questions

Is Jamie&#039;s Front-End Editor for Content Teams safe to use?

Jamie&#039;s Front-End Editor for Content Teams passes WP HealthKit's 49-layer security audit with flying colours, earning a Grade A with only 15 minor findings.

How many vulnerabilities does Jamie&#039;s Front-End Editor for Content Teams have?

WP HealthKit's audit found 15 findings for Jamie&#039;s Front-End Editor for Content Teams: 0 critical, 1 high, and 12 medium severity issues.

What is Jamie&#039;s Front-End Editor for Content Teams's security grade?

Jamie&#039;s Front-End Editor for Content Teams has an overall security grade of A (Excellent) based on WP HealthKit's 49-layer security audit.