tyhpdef / defuse-php-encryption

2.4.0 2026-10-05 14:34 UTC

Requires

• tyhpdef/defuse-php-encryption-impl: ~2.4.0.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 14:35 UTC

README

tyhpdef/defuse-php-encryption

Tyhp type definitions for defuse/php-encryption 2.4.0.

composer require --dev tyhpdef/defuse-php-encryption:2.4.0

This is a metapackage. Composer also installs tyhpdef/defuse-php-encryption-impl (type files). Require this name, not tyhpdef/defuse-php-encryption-impl.

See https://tyhplang.com.

Maintain defuse/php-encryption? Ship the types yourself

If you are a Packagist maintainer of defuse/php-encryption, you can take over these types.

Copy _tyhpdef/ from tyhpdef/defuse-php-encryption-impl (Apache-2.0; keep the NOTICE). Then either:

1. Bundle the files in defuse/php-encryption and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/defuse-php-encryption": "self.version" }, or
2. Publish a sibling types package under your vendor, versioned with defuse/php-encryption (same X.Y.Z). Set extra.tyhp.package there, require defuse/php-encryption with a real constraint, "replace": { "tyhpdef/defuse-php-encryption": "self.version" }, and set extra.tyhp.tyhpdef on defuse/php-encryption to your sibling’s Composer name.

Ship that to Packagist first, then open an issue:

https://github.com/tyhpproject/tyhp-runtime-src/issues/new?template=tyhpdef-ownership.yml

We verify Packagist ownership and that the types parse and cover the PHP API, then stop publishing community tags for those versions. We do not transfer the tyhpdef/defuse-php-encryption Packagist name.

Full process: TYHPDEF_OWNERSHIP.md in https://github.com/tyhpproject/tyhp-runtime-src