This page lists the PHP libraries, frameworks and build tools Niro was tested against, and whether it recognised each one.

What the marks mean.

The test code is made up for the purpose: one small service per library, with the names invented. So "supported" means Niro recognised it there. It is good evidence, but it is not a promise about every codebase. If Niro misses something in your code, the coverage audit reports the gap on its own (see Coverage audit).

Web frameworks and HTTP servers (the routes your code serves)

6 supported, 2 partly, 8 not yet.

Name Status Ways of using it that were tested
api-platform/core not yet no: #[ApiResource(operations: [new Get(), new GetCollection(), new Post()])] on an entity
cakephp/cakephp not yet no: config/routes.php: $builder->connect(path, [controller, action]), ->get, ->resources
codeigniter4/framework not yet no: app/Config/Routes.php: $routes->get('vendors', 'Vendors::index'), group, resource
laminas/laminas-mvc not yet no: module.config.php router routes with type Literal and 'route' => path
Laravel Folio supported yes: resources/views/pages/<path>.blade.php is a GET route at /<path>; nested folders nest the path
yes: index.blade.php is the root of its folder: pages/index.blade.php -> /, pages/plants/index.blade.php -> /plants
yes: a bracketed file name is a path parameter: [id], a model binding [Plant], or a keyed binding [Plant:slug] (on Windows [Plant-slug])
yes: [...name].blade.php captures several segments
yes: Folio::path(resource_path('views/<folder>'))->uri('/prefix') in a service provider mounts another pages folder under a prefix
laravel/framework partly yes: Route::get(path, closure) in routes/web.php
yes: Route::post(path, [Controller::class, 'method'])
yes: Route::put(path, 'Controller@method') legacy string
yes: Route::prefix('admin')->group(closure)
no: Route::resource(name, Controller::class) expands to seven routes
yes: routes/api.php served under /api by the framework
yes: Route::match(['get','post'], path, handler)
laravel/lumen-framework not yet no: $router->get(path, 'Controller@method') in routes/web.php
no: $router->group(['prefix' => 'v2'], closure)
league/route supported yes: $router->map('GET', path, [Controller::class, 'm']) and ->group
mezzio/mezzio supported yes: config/routes.php: $app->get(path, Handler::class) and ->route(path, H, [verbs])
nikic/fast-route supported yes: $r->addRoute('GET', path, handler) in simpleDispatcher
yes: $r->get(path) and $r->addGroup(prefix, closure)
slim/slim supported yes: $app->get(path, closure)
yes: $app->group(prefix, fn (RouteCollectorProxy $group) => $group->post(...))
yes: $app->map(['GET','POST'], path, closure)
spatie/laravel-route-attributes supported yes: #[Prefix] on class, #[Get]/#[Post] on methods
symfony/routing partly yes: #[Route(path, methods: [...])] on a controller method
yes: class-level #[Route('/catalog')] prefixes every method route
no: legacy docblock @Route("/path", methods={"GET"})
no: config/routes.yaml path + controller + methods
WordPress admin-ajax not yet no: add_action('wp_ajax_shop_refund', fn) served at POST /wp-admin/admin-ajax.php?action=shop_refund
WordPress REST API not yet no: register_rest_route(namespace, path, ['methods' => 'GET', 'callback' => fn]) on rest_api_init
yiisoft/yii2 not yet no: config urlManager rules 'GET loyalty' => 'loyalty/index'

The language's own HTTP server

1 supported, 1 partly, 1 not yet.

Name Status Ways of using it that were tested
PHP built-in ($_SERVER) not yet no: front controller: if on REQUEST_METHOD and parse_url(REQUEST_URI) path
no: switch ($path) { case '/health': ... }
no: preg_match('#^/receipts/(\d+)$#', $path) for a path parameter
PHP built-in (web server maps files) partly partly: one script per path: public/api/coupons.php checks REQUEST_METHOD
PHP built-in server / any document-root web server supported yes: <docroot>/<path>/index.php answers /<path>/ (a request that names no file gets the folder's index.php); the docroot comes from php -S -t, a Dockerfile or the web server config

HTTP client libraries (the calls your code makes to other services)

3 supported, 4 partly, 2 not yet.

Name Status Ways of using it that were tested
guzzlehttp/guzzle partly yes: new Client(['base_uri' => ...]) then $client->get(relative path)
yes: $client->request('POST', absolute url, options)
yes: $client->getAsync(url)->wait()
no: $client->send(new Request('DELETE', url))
yes: ClientInterface injected into a typed property, $this->http->post(url)
partly: base_uri read from getenv() set in docker-compose
yes: $client->requestAsync('GET', url)
kriswallsmith/buzz supported yes: $browser->get(url) on Buzz\Browser
laravel/framework (Http facade) partly yes: Http::get(absolute url)
partly: Http::withToken($t)->post(url) and other option chains
partly: Http::baseUrl(config('services.x.url'))->get(path), config from env()
no: Http::pool(fn (Pool $pool) => [$pool->get(url), ...])
psr/http-client (PSR-18) not yet no: $client->sendRequest($factory->createRequest('GET', url))
rmccue/requests supported yes: WpOrg\Requests\Requests::get(url) and ::post(url, headers, data)
saloonphp/saloon not yet no: Connector::resolveBaseUrl() plus Request $method and resolveEndpoint()
several (main project) supported yes: main calls a server in each framework through a different client form
symfony/http-client partly yes: HttpClient::create()->request('GET', url)
yes: HttpClientInterface injected, $this->client->request('POST', url)
yes: HttpClient::createForBaseUri(base)->request('GET', path)
partly: scoped client base_uri in framework.yaml, injected by name
WordPress HTTP API partly partly: wp_remote_get(url), wp_remote_post(url, args), wp_remote_request(url, ['method' => ...])

The language's own HTTP client

1 supported, 1 partly, 0 not yet.

Name Status Ways of using it that were tested
ext-curl partly yes: curl_init(url) then curl_exec
partly: curl_init() then curl_setopt($ch, CURLOPT_URL, url) and CURLOPT_POST
no: curl_setopt_array($ch, [CURLOPT_URL => url, CURLOPT_CUSTOMREQUEST => 'PATCH'])
yes: curl_multi_add_handle with handles from curl_init(url)
PHP streams (allow_url_fopen) supported yes: file_get_contents(absolute url)
yes: file_get_contents(url, false, stream_context_create(['http' => ['method' => 'POST']]))
yes: fopen(url, 'r') then stream_get_contents

gRPC

2 supported, 0 partly, 0 not yet.

Name Status Ways of using it that were tested
grpc/grpc supported yes: new {S}Client($addr, ['credentials' => ...]) then $client->PlaceOrder($req)->wait()
yes: $call = $client->ListOrders($req); foreach ($call->responses() as $x)
yes: hand-written BaseStub subclass calling $this->_simpleRequest('/pkg.S/M', ...)
spiral/roadrunner-grpc supported yes: class X implements {S}Interface, registered with $server->registerService({S}Interface::class, new X())

Databases and data stores

13 supported, 4 partly, 3 not yet.

Name Status Ways of using it that were tested
aws/aws-sdk-php (DynamoDB) supported yes: $ddb->putItem(['TableName' => 'carts', ...]) and query
aws/aws-sdk-php (S3) supported yes: $s3->putObject(['Bucket' => 'shop-invoices', ...]) and getObject
catfan/medoo supported yes: $db->select('newsletters', [...]) and $db->insert('newsletters', [...])
cycle/orm not yet no: #[Entity(table: 'loyalty_points')] and $orm->getRepository(X::class)->findAll()
doctrine/dbal partly yes: $conn->executeQuery(sql) and fetchAllAssociative(sql)
yes: $conn->insert('stock_moves', [...]) with the table as argument 0
no: $conn->createQueryBuilder()->select('*')->from('suppliers')
doctrine/orm supported yes: $em->getRepository(Product::class)->findBy([...]) with #[ORM\Table(name: 'products')]
yes: $em->persist($product); $em->flush()
yes: custom repository createQueryBuilder and createQuery(DQL)
elasticsearch/elasticsearch supported yes: $client->index(['index' => 'products', ...]) and search
ext-memcached supported yes: $m = new Memcached(); $m->addServer(...); $m->set(key, value)
ext-pgsql (built-in) supported yes: pg_query($conn, sql) and pg_query_params($conn, sql, params)
ext-redis (phpredis) supported yes: $r = new Redis(); $r->connect('redis', 6379); $r->hSet(...)
illuminate/database (Eloquent) partly yes: Order::where(...)->get() on a model with protected $table
yes: Order::create($data)
yes: model without $table: table is the plural snake case of the class (Coupon -> coupons)
no: DB::table('ledger_entries')->insert([...])
no: DB::select('SELECT * FROM refunds WHERE ...', [...])
laminas/laminas-db supported yes: new TableGateway('gift_cards', $adapter); $table->select([...])
laravel/framework (Cache facade) not yet no: Cache::put(key, value) and Cache::remember(key, ttl, fn)
laravel/framework (Redis facade) supported yes: Redis::incr('visits')
laravel/framework (Storage facade) supported yes: Storage::disk('s3')->put(path, contents)
mongodb/mongodb not yet no: $client->shop->reviews->insertOne(...) (database and collection as properties)
no: $client->selectCollection('shop', 'ratings')->find(...)
mysqli (built-in) supported yes: $db = new mysqli(...); $db->query('SELECT * FROM customers')
yes: $db->prepare(sql); bind_param; execute
yes: mysqli_query($link, sql) procedural form
PDO (built-in) partly yes: $pdo->query('SELECT ... FROM orders')
no: $stmt = $pdo->prepare(sql); $stmt->execute([...])
partly: $pdo->exec('DELETE FROM carts ...')
no: new PDO('pgsql:...') then prepare/execute an UPDATE
predis/predis supported yes: $redis = new Predis\Client('tcp://redis:6379'); $redis->set(key), get, lpush
several (main project) partly partly: main writes tables and topics that services read

Messaging and events (queues, topics, streams)

4 supported, 6 partly, 5 not yet.

Name Status Ways of using it that were tested
aws/aws-sdk-php (SNS) supported yes: $sns->publish(['TopicArn' => arn, 'Message' => ...])
aws/aws-sdk-php (SQS) partly partly: $sqs->sendMessage(['QueueUrl' => url, ...]) and receiveMessage
bernard/bernard not yet no: $producer->produce(new PlainMessage('ResizeImage', [...]))
enqueue/enqueue not yet no: $context->createProducer()->send($context->createQueue('audit'), $message)
ext-rdkafka supported yes: $producer->newTopic('payments')->produce(RD_KAFKA_PARTITION_UA, 0, $payload)
yes: $consumer->subscribe(['payments-settled']) then consume()
google/cloud-pubsub supported yes: $pubsub->topic('loyalty-events')->publish([...]) and subscription(...)->pull()
laravel/framework (events) supported yes: event(new OrderShipped($order)) helper
yes: OrderShipped::dispatch($id) and Event::dispatch(new OrderShipped)
yes: Event::listen(OrderShipped::class, [Listener::class, 'handle']) and $listen map
laravel/framework (queues) not yet no: SendInvoiceEmail::dispatch($order)->onQueue('emails')
no: dispatch(new SendInvoiceEmail($id)) global helper
no: Queue::pushOn('emails', new Job)
no: class implements ShouldQueue with handle()
pda/pheanstalk partly partly: $p->useTube('thumbnails'); $p->put(data) and watch/reserve
php-amqplib/php-amqplib not yet no: $channel->basic_publish($msg, 'orders', 'order.created')
no: $channel->basic_consume('invoice-requests', '', ..., $callback) in a worker script
php-mqtt/client partly partly: $mqtt->publish('devices/scale/weight', ...) and subscribe('devices/+/weight', fn)
predis/predis partly partly: $redis->publish('price-changes', ...) and $redis->pubSubLoop()->subscribe('price-changes')
symfony/event-dispatcher partly yes: $dispatcher->dispatch(new StockLow($sku), 'stock.low')
partly: #[AsEventListener(event: 'stock.low')]
partly: EventSubscriberInterface::getSubscribedEvents() returning ['stock.low' => 'onStockLow']
symfony/messenger partly yes: $this->bus->dispatch(new OrderPlaced($id)) on MessageBusInterface
partly: #[AsMessageHandler] class with __invoke(OrderPlaced $m)
yes: class implements MessageHandlerInterface (before 6.2)
twilio/sdk not yet no: $twilio->messages->create($to, ['from' => ..., 'body' => ...])

Build tools and package managers

3 supported, 0 partly, 0 not yet.

Name Status Ways of using it that were tested
composer supported yes: one composer.json, PSR-4 src/, public/index.php, tests/, vendor/
yes: apps/* require a library from packages/* through a path repository
yes: autoload classmap of a lib/ folder (no namespaces) and a files autoload of global functions
yes: a console tool: composer.json "bin" names bin/shopctl; no front controller
composer (symplify/monorepo-builder) supported yes: root composer.json maps every package namespace and replaces the packages; each package has its own composer.json
none (plain PHP) supported yes: plain PHP without Composer: index.php with require_once of lib/.php and includes/.inc

Project and folder layouts

8 supported, 0 partly, 0 not yet.

Name Status Ways of using it that were tested
Drupal supported yes: Drupal recommended-project: core in web/core, contrib in web/modules/contrib, own code in web/modules/custom/<m> with a .module hooks file
laravel supported yes: a Laravel app: artisan, app/, routes/, bootstrap/cache (generated), storage/framework/views (compiled Blade)
laravel + nwidart/laravel-modules supported yes: Modules/<Name>/ each with module.json and composer.json, loaded into one Laravel app
Magento 2 supported yes: app/code/<Vendor>/<Module> with registration.php and etc/module.xml; generated/ holds interceptors
PHPUnit, Pest, Codeception, phpspec supported yes: a library with tests/Unit (PHPUnit), tests/Feature (Pest), tests/Acceptance (Codeception Cest) and spec/ (phpspec)
symfony supported yes: a Symfony app (bin/console, public/index.php) with a local bundle through a path repository; var/cache holds the generated container
yes: apps/orders-api (HTTP), apps/billing-worker (bin/console messenger:consume only), packages/shared-kernel
WordPress supported yes: a WordPress site: core in wp-includes/ and wp-admin/, own plugin and theme in wp-content/, a third-party plugin beside it
WordPress (roots/bedrock) supported yes: Bedrock: composer.json installs core to web/wp and plugins to web/app/plugins; own code in web/app/mu-plugins