Psalm

Also announcing the public beta of Psalm v7, with up to 10x performance improvements for security analysis, a new combined analysis mode and much more! blog.daniil.it/2025/07/10/psa…

@psalmphp I've also contributed the underlying deepbind patch to upstream PHP, and it will be available for everyone to use in PHP 8.5! github.com/php/php-src/pu…

Announcing the official, hyperoptimized Psalm docker image, +50% faster than Psalm on normal PHP! blog.daniil.it/2025/07/10/off…

@infection_php @phpstan Posted an implementation tip: switching infection to amphp/parallel with our ForkContext would be great for performance, and would also allow super simple Psalm integration!

So now we have an experimental @phpstan integration in Infection, by `--static-analysis-plugin=phpstan`. Let's try to do the same for @psalmphp - created a feature request to make it possible: github.com/vimeo/psalm/di… Give it some love!

Introducing the new psalm-review tool: blog.daniil.it/2025/05/18/psa…

Announcing a new series of blogposts about Psalm v6's innovative performance improvements! Starting with Psalm 6.1 Deep Dive: Copy-on-Write + dynamic task dispatching: blog.daniil.it/2025/05/11/psa…

Announcing the release of Psalm v6! blog.daniil.it/2025/05/11/psa…

Psalm 5 is out! To symbolise this tremendous group effort we've translated the announcement into all the languages of Psalm's maintainers: psalm.dev/articles/psalm…

@jwage @nateritter @phpstan Psalm has a few features like security analysis and unused code detection, along with more rigorous analysis of if statements

@nateritter @psalmphp @phpstan Very similar. Psalm might be a little more strict and have more features. Or it did. Not sure now.

Running @psalmphp on my tests code has been a good decision so far. Makes it far easier to keep tests updated. Automation for the win!

@jwage You ready to make your code ludicrously safe? Then set rememberPropertyAssignmentsAfterCall to false, set findUnusedCode to true, ensureArrayStringOffsetsExist to true and ensureArrayIntOffsetsExist to true.

What other painfully strict @psalmphp settings should I enable in my project? #maxpain

@suckup_de Yup exactly

@psalmphp Something like this? docs.hhvm.com/hack/generics/…

If people want PHP generics then someone should create an RFC for erased-at-runtime generics. Erased-at-runtime types in PHP would be an insurmountable language shift for some voters, but maybe there’s enough support to carry it through.

@MabarDev The PHP project will probably never have an official typechecker. That doesn’t prevent it having syntax support for generics

@psalmphp Wouldn't that potentially break all the code using native generics once type checking is implemented? We would end up with another declare(validate_generics = 1);

It’s very unlikely that generics would be The Thing That Finally Makes Doubters Take PHP Seriously. But support for generics in PHP syntax (vs docblocks) would make a lot of code a little more beautiful than it is today.

All the major static analysis tools would quickly adapt, and there’s precedent in Python, which added support for type-erased generics (without a bundled typechecker to accompany that change).

Wrote a @psalmphp plugin to ensure I'm marking classes as final properly. If a concrete class does need to be inherited you can mark it with an Attribute to suppress the error. #php github.com/cspray/phinal

The literal-string type continues to do good work! It's now also supported in @phpstan (thx to @craigfrancis), which caught a SQL injection bug here: forum.nette.org/cs/35223-phpst…

@charlesspray I think classname would work better, mainly because that doesn't have three s in a row (so more resistant to typos)

Ok, so I updated this to basically be an RFC to bring the `class-string` type, similar to @psalmphp, into internals.

I have a #php idea but I'm not sure if it is worth pursuing or not. gist.github.com/cspray/0f4e67e…

@jwage @THROWS No, but you could make a PR — the functionality shouldn't be too tricky to add.

@psalmphp Do any tools exist to add @throws docblocks everywhere automatically?

Can @psalmphp help with erroring on unhandled exceptions or what is the best way to improve this in a codebase?