Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2025-05-25 12:40
📄 .actrc # Configuration file for nektos/act. # See https://github.com/nektos/act#configuration -P ubuntu-latest=shivammathur/node:latest	129 B	2025-05-25 12:40
📄 .distignore .DS_Store .git .gitignore .gitlab-ci.yml .editorconfig .travis.yml behat.yml circle.yml phpcs.xml.dist phpunit.xml.dist bin/ features/ utils/ .zip .tar.gz	157 B	2025-05-25 12:40
📄 .editorconfig # This file is for unifying the coding style for different editors and IDEs # editorconfig.org # WordPress Coding Standards # https://make.wordpress.org/core/handbook/coding-standards/ # From https://github.com/WordPress/wordpress-develop/blob/trunk/.editorconfig with a couple of additions. root = true [] charset = utf-8 end_of_line = lf insert_final_newline = true trim_trailing_whitespace = true indent_style = tab [{.yml,.feature,.jshintrc,.json}] indent_style = space indent_size = 2 [.md] trim_trailing_whitespace = false [{.txt,wp-config-sample.php}] end_of_line = crlf	591 B	2025-05-25 12:40
📁 .git	-	2026-01-07 15:08
📁 .github	-	2025-05-25 12:40
📄 .gitignore .DS_Store wp-cli.local.yml node_modules/ vendor/ .zip .tar.gz composer.lock *.log phpunit.xml phpcs.xml .phpcs.xml	117 B	2025-05-25 12:40
📄 AGENTS.md # Instructions This package is part of WP-CLI, the official command line interface for WordPress. For a detailed explanation of the project structure and development workflow, please refer to the main @README.md file. ## Best Practices for Code Contributions When contributing to this package, please adhere to the following guidelines: * Follow Existing Conventions: Before writing any code, analyze the existing codebase in this package to understand the coding style, naming conventions, and architectural patterns. * Focus on the Package's Scope: All changes should be relevant to the functionality of the package. * Write Tests: All new features and bug fixes must be accompanied by acceptance tests using Behat. You can find the existing tests in the `features/` directory. There may be PHPUnit unit tests as well in the `tests/` directory. * Update Documentation: If your changes affect the user-facing functionality, please update the relevant inline code documentation. ### Building and running Before submitting any changes, it is crucial to validate them by running the full suite of static code analysis and tests. To run the full suite of checks, execute the following command: `composer test`. This single command ensures that your changes meet all the quality gates of the project. While you can run the individual steps separately, it is highly recommended to use this single command to ensure a comprehensive validation. ### Useful Composer Commands The project uses Composer to manage dependencies and run scripts. The following commands are available: * `composer install`: Install dependencies. * `composer test`: Run the full test suite, including linting, code style checks, static analysis, and unit/behavior tests. * `composer lint`: Check for syntax errors. * `composer phpcs`: Check for code style violations. * `composer phpcbf`: Automatically fix code style violations. * `composer phpstan`: Run static analysis. * `composer phpunit`: Run unit tests. * `composer behat`: Run behavior-driven tests. ### Coding Style The project follows the `WP_CLI_CS` coding standard, which is enforced by PHP_CodeSniffer. The configuration can be found in `phpcs.xml.dist`. Before submitting any code, please run `composer phpcs` to check for violations and `composer phpcbf` to automatically fix them. ## Documentation The `README.md` file might be generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). In that case, changes need to be made against the corresponding part of the codebase. ### Inline Documentation Only write high-value comments if at all. Avoid talking to the user through comments. ## Testing The project has a comprehensive test suite that includes unit tests, behavior-driven tests, and static analysis. * Unit tests are written with PHPUnit and can be found in the `tests/` directory. The configuration is in `phpunit.xml.dist`. * Behavior-driven tests are written with Behat and can be found in the `features/` directory. The configuration is in `behat.yml`. * Static analysis is performed with PHPStan. All tests are run on GitHub Actions for every pull request. When writing tests, aim to follow existing patterns. Key conventions include: * When adding tests, first examine existing tests to understand and conform to established conventions. * For unit tests, extend the base `WP_CLI\Tests\TestCase` test class. * For Behat tests, only WP-CLI commands installed in `composer.json` can be run. ### Behat Steps WP-CLI makes use of a Behat-based testing framework and provides a set of custom step definitions to write feature tests. > Note: If you are expecting an error output in a test, you need to use `When I try ...` instead of `When I run ...` . #### Given * `Given an empty directory` - Creates an empty directory. * `Given /^an? (empty\|non-existent) ([^\s]+) directory$/` - Creates or deletes a specific directory. * `Given an empty cache` - Clears the WP-CLI cache directory. * `Given /^an? ([^\s]+) (file\|cache file):$/` - Creates a file with the given contents. * `Given /^"([^"]+)" replaced with "([^"]+)" in the ([^\s]+) file$/` - Search and replace a string in a file using regex. * `Given /^that HTTP requests to (.?) will respond with:$/` - Mock HTTP requests to a given URL. `Given WP files` - Download WordPress files without installing. * `Given wp-config.php` - Create a wp-config.php file using `wp config create`. * `Given a database` - Creates an empty database. * `Given a WP install(ation)` - Installs WordPress. * `Given a WP install(ation) in :subdir` - Installs WordPress in a given directory. * `Given a WP install(ation) with Composer` - Installs WordPress with Composer. * `Given a WP install(ation) with Composer and a custom vendor directory :vendor_directory` - Installs WordPress with Composer and a custom vendor directory. * `Given /^a WP multisite (subdirectory\|subdomain)?\s?(install\|installation)$/` - Installs WordPress Multisite. * `Given these installed and active plugins:` - Installs and activates one or more plugins. * `Given a custom wp-content directory` - Configure a custom `wp-content` directory. * `Given download:` - Download multiple files into the given destinations. * `Given /^save (STDOUT\|STDERR) ([\'].+[^\'])?\s?as \{(\w+)\}$/` - Store STDOUT or STDERR contents in a variable. * `Given /^a new Phar with (?:the same version\|version "([^"]+)")$/` - Build a new WP-CLI Phar file with a given version. * `Given /^a downloaded Phar with (?:the same version\|version "([^"]+)")$/` - Download a specific WP-CLI Phar version from GitHub. * `Given /^save the (.+) file ([\'].+[^\'])? as \{(\w+)\}$/` - Stores the contents of the given file in a variable. * `Given a misconfigured WP_CONTENT_DIR constant directory` - Modify wp-config.php to set `WP_CONTENT_DIR` to an empty string. * `Given a dependency on current wp-cli` - Add `wp-cli/wp-cli` as a Composer dependency. * `Given a PHP built-in web server` - Start a PHP built-in web server in the current directory. * `Given a PHP built-in web server to serve :subdir` - Start a PHP built-in web server in the given subdirectory. #### When * ``When /^I launch in the background `([^`]+)`$/`` - Launch a given command in the background. * ``When /^I (run\|try) `([^`]+)`$/`` - Run or try a given command. * ``When /^I (run\|try) `([^`]+)` from '([^\s]+)'$/`` - Run or try a given command in a subdirectory. * `When /^I (run\|try) the previous command again$/` - Run or try the previous command again. #### Then * `Then /^the return code should( not)? be (\d+)$/` - Expect a specific exit code of the previous command. * `Then /^(STDOUT\|STDERR) should( strictly)? (be\|contain\|not contain):$/` - Check the contents of STDOUT or STDERR. * `Then /^(STDOUT\|STDERR) should be a number$/` - Expect STDOUT or STDERR to be a numeric value. * `Then /^(STDOUT\|STDERR) should not be a number$/` - Expect STDOUT or STDERR to not be a numeric value. * `Then /^STDOUT should be a table containing rows:$/` - Expect STDOUT to be a table containing the given rows. * `Then /^STDOUT should end with a table containing rows:$/` - Expect STDOUT to end with a table containing the given rows. * `Then /^STDOUT should be JSON containing:$/` - Expect valid JSON output in STDOUT. * `Then /^STDOUT should be a JSON array containing:$/` - Expect valid JSON array output in STDOUT. * `Then /^STDOUT should be CSV containing:$/` - Expect STDOUT to be CSV containing certain values. * `Then /^STDOUT should be YAML containing:$/` - Expect STDOUT to be YAML containing certain content. * `Then /^(STDOUT\|STDERR) should be empty$/` - Expect STDOUT or STDERR to be empty. * `Then /^(STDOUT\|STDERR) should not be empty$/` - Expect STDOUT or STDERR not to be empty. * `Then /^(STDOUT\|STDERR) should be a version string (<\|<=\|>\|>=\|==\|=\|<>) ([+\w.{}-]+)$/` - Expect STDOUT or STDERR to be a version string comparing to the given version. * `Then /^the (.+) (file\|directory) should( strictly)? (exist\|not exist\|be:\|contain:\|not contain):$/` - Expect a certain file or directory to (not) exist or (not) contain certain contents. * `Then /^the contents of the (.+) file should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match file contents against a regex. `Then /^(STDOUT\|STDERR) should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match STDOUT or STDERR against a regex. `Then /^an email should (be sent\|not be sent)$/` - Expect an email to be sent (or not). * `Then the HTTP status code should be :code` - Expect the HTTP status code for visiting `http://localhost:8080`.	8.48 KB	2026-01-07 15:08
📄 CONTRIBUTING.md Contributing ============ We appreciate you taking the initiative to contribute to this project. Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. For a more thorough introduction, [check out WP-CLI's guide to contributing](https://make.wordpress.org/cli/handbook/contributing/). This package follows those policy and guidelines.	538 B	2025-05-25 12:40
📄 LICENSE The MIT License (MIT) Copyright (C) 2011-2018 WP-CLI Development Group (https://github.com/wp-cli/checksum-command/contributors) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.	1.13 KB	2025-05-25 12:40
📄 README.md wp-cli/checksum-command ======================= Verifies file integrity by comparing to published checksums. [![Testing](https://github.com/wp-cli/checksum-command/actions/workflows/testing.yml/badge.svg)](https://github.com/wp-cli/checksum-command/actions/workflows/testing.yml) Quick links: [Using](#using) \| [Installing](#installing) \| [Contributing](#contributing) \| [Support](#support) ## Using This package implements the following commands: ### wp core verify-checksums Verifies WordPress files against WordPress.org's checksums. ~~~ wp core verify-checksums [--include-root] [--version=<version>] [--locale=<locale>] [--insecure] [--exclude=<files>] [--format=<format>] ~~~ Downloads md5 checksums for the current version from WordPress.org, and compares those checksums against the currently installed files. For security, avoids loading WordPress when verifying checksums. If you experience issues verifying from this command, ensure you are passing the relevant `--locale` and `--version` arguments according to the values from the `Dashboard->Updates` menu in the admin area of the site. OPTIONS [--include-root] Verify all files and folders in the root directory, and warn if any non-WordPress items are found. [--version=<version>] Verify checksums against a specific version of WordPress. [--locale=<locale>] Verify checksums against a specific locale of WordPress. [--insecure] Retry downloads without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack. [--exclude=<files>] Exclude specific files from the checksum verification. Provide a comma-separated list of file paths. [--format=<format>] Render output in a specific format. When provided, messages are displayed in the chosen format. --- default: plain options: - plain - table - json - csv - yaml - count --- EXAMPLES # Verify checksums $ wp core verify-checksums Success: WordPress installation verifies against checksums. # Verify checksums for given WordPress version $ wp core verify-checksums --version=4.0 Success: WordPress installation verifies against checksums. # Verify checksums for given locale $ wp core verify-checksums --locale=en_US Success: WordPress installation verifies against checksums. # Verify checksums for given locale $ wp core verify-checksums --locale=ja Warning: File doesn't verify against checksum: wp-includes/version.php Warning: File doesn't verify against checksum: readme.html Warning: File doesn't verify against checksum: wp-config-sample.php Error: WordPress installation doesn't verify against checksums. # Verify checksums and exclude files $ wp core verify-checksums --exclude="readme.html" Success: WordPress installation verifies against checksums. # Verify checksums with formatted output $ wp core verify-checksums --format=json [{"file":"readme.html","message":"File doesn't verify against checksum"}] Error: WordPress installation doesn't verify against checksums. ### wp plugin verify-checksums Verifies plugin files against WordPress.org's checksums. ~~~ wp plugin verify-checksums [<plugin>...] [--all] [--strict] [--version=<version>] [--format=<format>] [--insecure] [--exclude=<name>] ~~~ OPTIONS [<plugin>...] One or more plugins to verify. [--all] If set, all plugins will be verified. [--strict] If set, even "soft changes" like readme.txt changes will trigger checksum errors. [--version=<version>] Verify checksums against a specific plugin version. [--format=<format>] Render output in a specific format. --- default: table options: - table - json - csv - yaml - count --- [--insecure] Retry downloads without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack. [--exclude=<name>] Comma separated list of plugin names that should be excluded from verifying. EXAMPLES # Verify the checksums of all installed plugins $ wp plugin verify-checksums --all Success: Verified 8 of 8 plugins. # Verify the checksums of a single plugin, Akismet in this case $ wp plugin verify-checksums akismet Success: Verified 1 of 1 plugins. ## Installing This package is included with WP-CLI itself, no additional installation necessary. To install the latest version of this package over what's included in WP-CLI, run: wp package install git@github.com:wp-cli/checksum-command.git ## Contributing We appreciate you taking the initiative to contribute to this project. Contributing isn’t limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. For a more thorough introduction, [check out WP-CLI's guide to contributing](https://make.wordpress.org/cli/handbook/contributing/). This package follows those policy and guidelines. ### Reporting a bug Think you’ve found a bug? We’d love for you to help us get it fixed. Before you create a new issue, you should [search existing issues](https://github.com/wp-cli/checksum-command/issues?q=label%3Abug%20) to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version. Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please [create a new issue](https://github.com/wp-cli/checksum-command/issues/new). Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, [review our bug report documentation](https://make.wordpress.org/cli/handbook/bug-reports/). ### Creating a pull request Want to contribute a new feature? Please first [open a new issue](https://github.com/wp-cli/checksum-command/issues/new) to discuss whether the feature is a good fit for the project. Once you've decided to commit the time to seeing your pull request through, [please follow our guidelines for creating a pull request](https://make.wordpress.org/cli/handbook/pull-requests/) to make sure it's a pleasant experience. See "[Setting up](https://make.wordpress.org/cli/handbook/pull-requests/#setting-up)" for details specific to working on this package locally. ## Support GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support This README.md is generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). To suggest changes, please submit a pull request against the corresponding part of the codebase.	6.67 KB	2026-01-07 15:08
📄 behat.yml default: suites: default: contexts: - WP_CLI\Tests\Context\FeatureContext paths: - features	126 B	2025-05-25 12:40
📄 checksum-command.php <?php if ( ! class_exists( 'WP_CLI' ) ) { return; } $wpcli_checksum_autoloader = __DIR__ . '/vendor/autoload.php'; if ( file_exists( $wpcli_checksum_autoloader ) ) { require_once $wpcli_checksum_autoloader; } WP_CLI::add_command( 'core', 'Core_Command_Namespace' ); WP_CLI::add_command( 'core verify-checksums', 'Checksum_Core_Command' ); WP_CLI::add_command( 'plugin', 'Plugin_Command_Namespace' ); WP_CLI::add_command( 'plugin verify-checksums', 'Checksum_Plugin_Command' );	483 B	2025-05-25 12:40
📄 composer.json { "name": "wp-cli/checksum-command", "type": "wp-cli-package", "description": "Verifies file integrity by comparing to published checksums.", "homepage": "https://github.com/wp-cli/checksum-command", "license": "MIT", "authors": [ { "name": "Daniel Bachhuber", "email": "daniel@runcommand.io", "homepage": "https://runcommand.io" } ], "require": { "wp-cli/wp-cli": "^2.12" }, "require-dev": { "wp-cli/extension-command": "^1.2 \|\| ^2", "wp-cli/wp-cli-tests": "^5" }, "config": { "process-timeout": 7200, "sort-packages": true, "allow-plugins": { "dealerdirect/phpcodesniffer-composer-installer": true, "johnpbloch/wordpress-core-installer": true, "phpstan/extension-installer": true }, "lock": false }, "extra": { "branch-alias": { "dev-main": "2.x-dev" }, "bundled": true, "commands": [ "core verify-checksums", "plugin verify-checksums" ] }, "autoload": { "classmap": [ "src/" ], "files": [ "checksum-command.php" ] }, "minimum-stability": "dev", "prefer-stable": true, "scripts": { "behat": "run-behat-tests", "behat-rerun": "rerun-behat-tests", "lint": "run-linter-tests", "phpcs": "run-phpcs-tests", "phpstan": "run-phpstan-tests", "phpcbf": "run-phpcbf-cleanup", "phpunit": "run-php-unit-tests", "prepare-tests": "install-package-tests", "test": [ "@lint", "@phpcs", "@phpstan", "@phpunit", "@behat" ] }, "support": { "issues": "https://github.com/wp-cli/checksum-command/issues" } }	1.87 KB	2026-01-07 15:08
📁 features	-	2026-01-07 15:08
📄 phpcs.xml.dist <?xml version="1.0"?> <ruleset name="WP-CLI-checksum"> <description>Custom ruleset for WP-CLI checksum-command</description> <!-- ############################################################################# COMMAND LINE ARGUMENTS For help understanding this file: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Annotated-ruleset.xml For help using PHPCS: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage ############################################################################# --> <!-- What to scan. --> <file>.</file> <!-- Show progress. --> <arg value="p"/> <!-- Strip the filepaths down to the relevant bit. --> <arg name="basepath" value="./"/> <!-- Check up to 8 files simultaneously. --> <arg name="parallel" value="8"/> <!-- ############################################################################# USE THE WP_CLI_CS RULESET ############################################################################# --> <rule ref="WP_CLI_CS"/> <!-- ############################################################################# PROJECT SPECIFIC CONFIGURATION FOR SNIFFS ############################################################################# --> <!-- For help understanding the `testVersion` configuration setting: https://github.com/PHPCompatibility/PHPCompatibility#sniffing-your-code-for-compatibility-with-specific-php-versions --> <config name="testVersion" value="7.2-"/> <!-- Verify that everything in the global namespace is either namespaced or prefixed. See: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#naming-conventions-prefix-everything-in-the-global-namespace --> <rule ref="WordPress.NamingConventions.PrefixAllGlobals"> <properties> <property name="prefixes" type="array"> <element value="WP_CLI\Checksum"/><!-- Namespaces. --> <element value="wpcli_checksum"/><!-- Global variables and such. --> </property> </properties> </rule> <!-- Exclude existing classes from the prefix rule as it would break BC to prefix them now. --> <rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedClassFound"> <exclude-pattern>/src/(Plugin_\|Core_)Command_Namespace\.php$</exclude-pattern> <exclude-pattern>/src/Checksum_(Plugin\|Core\|Base)_Command\.php$</exclude-pattern> </rule> <rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedNamespaceFound"> <exclude-pattern>*/src/WP_CLI/Fetchers/UnfilteredPlugin\.php$</exclude-pattern> </rule> </ruleset>	2.48 KB	2026-01-07 15:08
📄 phpstan.neon.dist parameters: level: 9 paths: - src - checksum-command.php scanDirectories: - vendor/wp-cli/wp-cli/php scanFiles: - vendor/php-stubs/wordpress-stubs/wordpress-stubs.php treatPhpDocTypesAsCertain: false ignoreErrors: - identifier: missingType.iterableValue - identifier: missingType.parameter - identifier: missingType.return	363 B	2026-01-07 15:08
📁 src	-	2026-01-07 15:08
📄 wp-cli.yml require: - checksum-command.php	34 B	2025-05-25 12:40

Terminal