Download the PHP package knplabs/phpstan-rules without Composer

On this page you can find all versions of the php package knplabs/phpstan-rules. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of knplabs/phpstan-rules

Informations about the package phpstan-rules

knplabs/phpstan-rules

CI PHP Packagist

PHPStan rules shared across KnpLabs organization projects.

Requirements

Installation

Using phpstan/extension-installer (recommended)

If you don't use phpstan/extension-installer, include the extension in your phpstan.neon:

Rules

clock.disallowDateTimeNow — PSR-20 Clock Abstraction

Enforces the PSR-20 recommendation to avoid instantiating DateTime or DateTimeImmutable with a relative or implicit date. This makes code that depends on the current time testable and respects the clock abstraction.

Triggers on:

Does not trigger on (absolute date strings and variables are allowed):

Recommended fix: inject Psr\Clock\ClockInterface and call $clock->now():

clock.disallowTimeFunctions — PSR-20 Clock Abstraction (functions)

Enforces the PSR-20 recommendation to avoid using time() or date() directly. This makes code that depends on the current time testable and respects the clock abstraction.

Triggers on:

Does not trigger on (explicit non-"now" timestamps are fine):

Recommended fix: inject Psr\Clock\ClockInterface and call $clock->now():

Contributing

See CONTRIBUTING.md for the human contributor guide.

If you are working with an AI agent, refer to AGENTS.md — it contains the AI-facing instructions for this repository.

Release & Publishing

Releases are fully automated with release-please and published to Packagist as soon as a GitHub release goes out.

Prerequisites (one-time setup)

  1. Register the package on Packagist — submit the repository once at packagist.org/packages/submit.

  2. Add repository secrets — in GitHub → Settings → Secrets and variables → Actions, create two repository secrets:

    Secret name Value
    PACKAGIST_USERNAME Your Packagist account username
    PACKAGIST_API_TOKEN An API token generated on your Packagist profile page

How it works

  1. Every push to main runs the Release workflow (.github/workflows/release.yml), which calls GoogleCloudPlatform/release-please-action. It parses Conventional Commits (feat:, fix:, doc:, etc.) since the last release and keeps a release PR up to date with the bumped version and generated CHANGELOG.md entry.
  2. Merging the release PR makes release-please tag the repository and publish the corresponding GitHub release automatically — no manual "Draft a new release" step is needed anymore.
  3. That GitHub release publish event triggers the Publish workflow, which notifies Packagist via its REST API.
  4. The new version appears on Packagist within a few minutes.

Commit messages matter — release-please only picks up a version bump when commits follow the Conventional Commits format. Non-conforming commits are ignored when computing the next version.

Manual re-trigger

If the Publish workflow fails or you need to re-sync Packagist without creating a new release:

  1. Go to Actions → Publish → Run workflow.
  2. Click Run workflow (no inputs required).

License

MIT — see LICENSE.

All versions of phpstan-rules with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
phpstan/phpstan Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package knplabs/phpstan-rules contains the following files

Loading the files please wait ...