# CoreFiles
> The original files of every Joomla and WordPress release, run by mySites.guru. Free, no API key, read-only GET requests.
Use it to tell whether a file on a Joomla or WordPress site is an unmodified core file, which release it came from, and what changed between releases. Hash the site's files where they are and send only the hashes; never upload a site's files.
Base URL: https://corefiles.mysites.guru
Platforms: joomla, wordpress. Versions as released, for example 5.4.0, 6.2.0-rc1, 7.1.4.
Add ?format=json to a page URL (/lookup, /pretty, /folder, /history, /diff, /stats) for the same data as JSON.
## Look up a file by its hash
GET /lookup/{md5 or sha256}?format=json&name={file name}
Lists every release and path that has this content. No matches means it is not a core file in any stored release. With name, "named" lists core files that have that file name, so you can fetch the original and compare.
## Read a core file
GET /raw/{platform}/{version}/{path} the file's bytes
GET /stat/{platform}/{version}/{path} md5, sha1, sha256 and size as JSON
GET /history/{platform}/{path}?format=json the releases where that file changed
## Compare releases
GET /diff/{platform}/{from}/{to}?format=json added, removed and changed files
GET /diff/{platform}/{from}/{to}/{path}?format=text a unified diff of one file
## Check a whole site
GET /hashes/{platform}/{version}/plain
Every core file in that release as path<TAB>md5. Hash the site's files and compare: a different md5 means a modified core file, and a file missing from the list is not core.
## Reading the answers
A 404 with X-Corefiles-Release: present means the path is not in that release, so the file is not core.
A 404 with X-Corefiles-Release: missing means that release is not stored yet. Treat the answer as unknown, never as "not core". New releases are added within the hour.
GET /releases.json lists every stored release.
Paste it into Claude, ChatGPT or Cursor. Agents can also read it at /llms.txt. On a lookup, file, history or compare page, Copy for your AI agent adds what that page shows.
class-wp-block-editor-context.php58 lines, 1,350 bytes, from wordpress-7.1.4.zip
<?php
/**
* Blocks API: WP_Block_Editor_Context class
*
* @package WordPress
* @since 5.8.0
*/
/**
* Contains information about a block editor being rendered.
*
* @since 5.8.0
*/
#[AllowDynamicProperties]
final class WP_Block_Editor_Context {
/**
* String that identifies the block editor being rendered. Can be one of:
*
* - `'core/edit-post'` - The post editor at `/wp-admin/edit.php`.
* - `'core/edit-widgets'` - The widgets editor at `/wp-admin/widgets.php`.
* - `'core/customize-widgets'` - The widgets editor at `/wp-admin/customize.php`.
* - `'core/edit-site'` - The site editor at `/wp-admin/site-editor.php`.
*
* Defaults to 'core/edit-post'.
*
* @since 6.0.0
*
* @var string
*/
public $name = 'core/edit-post';
/**
* The post being edited by the block editor. Optional.
*
* @since 5.8.0
*
* @var WP_Post|null
*/
public $post = null;
/**
* Constructor.
*
* Populates optional properties for a given block editor context.
*
* @since 5.8.0
*
* @param array $settings The list of optional settings to expose in a given context.
*/
public function __construct( array $settings = array() ) {
if ( isset( $settings['name'] ) ) {
$this->name = $settings['name'];
}
if ( isset( $settings['post'] ) ) {
$this->post = $settings['post'];
}
}
}