F-Droid Data metadata
F-Droid Data app metadata files
| Type | object |
|---|---|
| File match |
**/metadata/*.yml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/f-droid-data-metadata/latest.json |
| Source | https://gitlab.com/fdroid/fdroiddata/-/raw/master/schemas/metadata.json |
Validate with Lintel
npx @lintel/lintel check
For every app on F-Droid a metadata file in the format of
Properties
Any number of categories for the application to be placed in.
Any number of sub-entries can be present, each specifying a version to automatically build from source.
This determines the method used for auto-generating new builds when new releases are available - in other words, adding a new Build Version line to the metadata.
This determines the method using for determining when new releases are available - in other words, the updating of the CurrentVersion and CurrentVersionCode fields in the metadata by the fdroid checkupdates process.
The name of the version that is the recommended release. There may be newer versions of the application than this (e.g. unstable versions), and there will almost certainly be older ones.
The version code corresponding to the CurrentVersion field.
The name of the author, either full, abbreviated or pseudonym.
The e-mail address of the author(s).
The URL to donate to the project.
The project's Liberapay (https://liberapay.com) user or group name.
The project's OpenCollective (https://opencollective.com) user or group name.
A Bitcoin address for donating to the project.
A Litecoin address for donating to the project.
The title of the application, with optional descriptive phrase.
The name of the application as can best be retrieved from the source code.
DEPRECATED. A brief summary of what the application is. Should rather be provided via Fastlane.
DEPRECATED. A full description of the application, relevant to the latest version. Should rather be provided via Fastlane.
The lowercase hex value of the SHA-256 fingerprint of the signing certificate of an app. If an APK of that app is not signed by one of these keys, it will not be included in the repository.
This is a multi-line field using the same rules and syntax as the description. It's used to record notes for F-Droid maintainers to assist in maintaining and updating the application in the repository.
The type of repository - for automatic building from source.
The repository location. Usually a https:// URL, for example.
The location of binaries used in verification process.
If this field is present, the application does not get put into the public index. The value should be a description of why the application is disabled.
Whether the application requires root privileges to be usable.
This determines the number of versions to keep. The older versions of the app are moved to the archive repo, if one is configured. Defaults to 3.
A list of operations to be applied to the vercode obtained by the defined UpdateCheckMode. %c will be replaced by the actual vercode, and each string will be passed to python's eval function to calculate a version code.
When checking for updates (via UpdateCheckMode) this can be used to specify a regex which, if matched against the version name, causes that version to be ignored.
When checking for updates (via UpdateCheckMode) this can be used to specify the package name to search for. Useful when apps have a static package name but change it programmatically in some app flavors, by e.g. appending “.open” or “.free” at the end of the package name.
Used in conjunction with UpdateCheckMode for certain modes.
In case we are missing the source code for the CurrentVersion reported by Upstream, or that Non-Free elements have been introduced, this defines the first version that began to miss source code.