# 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.
OperationStateEnum.php45 lines, 1,347 bytes, from wordpress-7.0.2.zip
<?php
declare (strict_types=1);
namespace WordPress\AiClient\Operations\Enums;
use WordPress\AiClient\Common\AbstractEnum;
/**
* Enum for operation states.
*
* @since 0.1.0
*
* @method static self starting() Creates an instance for STARTING state.
* @method static self processing() Creates an instance for PROCESSING state.
* @method static self succeeded() Creates an instance for SUCCEEDED state.
* @method static self failed() Creates an instance for FAILED state.
* @method static self canceled() Creates an instance for CANCELED state.
* @method bool isStarting() Checks if the state is STARTING.
* @method bool isProcessing() Checks if the state is PROCESSING.
* @method bool isSucceeded() Checks if the state is SUCCEEDED.
* @method bool isFailed() Checks if the state is FAILED.
* @method bool isCanceled() Checks if the state is CANCELED.
*/
class OperationStateEnum extends AbstractEnum
{
/**
* Operation is starting.
*/
public const STARTING = 'starting';
/**
* Operation is processing.
*/
public const PROCESSING = 'processing';
/**
* Operation succeeded.
*/
public const SUCCEEDED = 'succeeded';
/**
* Operation failed.
*/
public const FAILED = 'failed';
/**
* Operation was canceled.
*/
public const CANCELED = 'canceled';
}