Skip to content
ExtensionFlowJoomla Update Platform
System OK
← Documentation Compatibility and trust

Compatibility labels and checksums

How to read Joomla/PHP compatibility, file size and checksum metadata before deploying a release.

Documentation Platform changelog Roadmap
01

What it is

Structured metadata attached to releases: supported Joomla versions, supported PHP versions, file size and checksums.

02

Why it helps

Teams can avoid installing a build outside its supported runtime or deploying a modified file accidentally.

03

How to use it

Compare labels against the target site, then verify the package with SHA256 when your workflow requires it.

Compatibility data and checksums reduce ambiguity before installation. They help installers match a release to the target Joomla and PHP runtime and verify the artifact when required.

Compatibility labels

Joomla and PHP badges represent the release compatibility matrix stored in ExtensionFlow. They are intended as quick signals before opening the detailed release page.

Checksum usage

The release artifact can expose SHA256, SHA384, SHA512 and MD5 values. SHA256/SHA384/SHA512 should be treated as stronger integrity values; MD5 remains useful only for legacy workflows that still record it.

sha256sum downloaded-extension.zip

When metadata is missing

If a release has notes but no artifact metadata, the file may not be available for download. The UI should show that state as view-only rather than pretending a download exists.