# 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-html-stack-event.php69 lines, 1,345 bytes, from wordpress-6.6-beta3.zip
<?php
/**
* HTML API: WP_HTML_Stack_Event class
*
* @package WordPress
* @subpackage HTML-API
* @since 6.6.0
*/
/**
* Core class used by the HTML Processor as a record for stack operations.
*
* This class is for internal usage of the WP_HTML_Processor class.
*
* @access private
* @since 6.6.0
*
* @see WP_HTML_Processor
*/
class WP_HTML_Stack_Event {
/**
* Refers to popping an element off of the stack of open elements.
*
* @since 6.6.0
*/
const POP = 'pop';
/**
* Refers to pushing an element onto the stack of open elements.
*
* @since 6.6.0
*/
const PUSH = 'push';
/**
* References the token associated with the stack push event,
* even if this is a pop event for that element.
*
* @since 6.6.0
*
* @var WP_HTML_Token
*/
public $token;
/**
* Indicates which kind of stack operation this event represents.
*
* May be one of the class constants.
*
* @since 6.6.0
*
* @see self::POP
* @see self::PUSH
*
* @var string
*/
public $operation;
/**
* Constructor function.
*
* @param WP_HTML_Token $token Token associated with stack event, always an opening token.
* @param string $operation One of self::PUSH or self::POP.
*/
public function __construct( $token, $operation ) {
$this->token = $token;
$this->operation = $operation;
}
}