Meta tags:
description= Definition of the .yml metadata for apps;
Headings (most frequently used words):
yaml, metadata,
Text of the page (most frequently used words):
the (74), app (36), for (19), are (16), name (11), fastlane (11), can (11), and (10), only (10), apk (10), optional (10), github (9), #metadata (9), releases (9), with (8), our (8), not (8), this (7), com (7), repository (7), yaml (7), used (6), available (6), list (6), but (6), file (6), https (6), apps (6), new (5), versioncode (5), where (5), release (5), format (5), url (5), they (5), usually (5), izzyondroid (5), you (5), mandatory (5), author (5), trase1 (5), simplestnotes (5), fields (4), check (4), repo (4), was (4), there (4), tags (4), which (4), version (4), changelogs (4), get (4), git (4), gitlab (4), method (4), txt (4), set (4), here (4), multiple (4), page (4), corresponding (4), website (4), these (3), per (3), files (3), how (3), regex (3), versionname (3), example (3), autoupdatemode (3), different (3), must (3), single (3), changelog (3), date (3), yyyy (3), any (3), when (3), from (3), values (3), codeberg (3), what (3), title (3), android (3), ghskippre (3), should (3), hosted (3), would (3), least (3), one (3), autoname (3), yml (3), donate (3), forge (3), translate (3), license (3), categories (3), antifeatures (3), google (3), contact (3), reproducible (3), builds (3), your (3), documentation (3), contributing (3), faq (3), started (3), about (3), currently (2), listings (2), more (2), older (2), historical (2), reasons (2), schema (2), definition (2), have (2), updatecheckmode (2), string (2), match (2), defines (2), source (2), code (2), build (2), value (2), 2000 (2), arm64 (2), each (2), followed (2), notes (2), above (2), place (2), than (2), import (2), comma (2), separated (2), include (2), fulldescmd (2), full_description (2), shortdesc (2), icon (2), screenshots (2), take (2), graphics (2), fastlanefeatures (2), added (2), useful (2), examples (2), debug (2), case (2), listed (2), need (2), them (2), find (2), self (2), removal (2), appadded (2), object (2), holding (2), maintainernotes (2), present (2), just (2), see (2), inclusion (2), policy (2), tree (2), service (2), funding (2), bitcoin (2), litecoin (2), donating (2), information (2), link (2), people (2), help (2), like (2), strongly (2), recommended (2), etc (2), issuetracker (2), sourcecode (2), additional (2), names (2), authorname (2), given (2), youtube (2), verification (2), hints (2), builders (2), developer (2), best (2), practices (2), general (2), resources (2), security (2), home (2), made, material, mkdocs, back, top, kept, yamls, full, please, refer, disable, update, all, because, archived, gone, entirely, none, similar, once, month, static, daily, matching, updates, framework, supports, both, same, time, could, written, always, integer, either, info, against, placeholders, tag, pointing, last, nosourcesince, cases, based, architecture, enclosed, quotes, subtract, 2021, flutter, vercodeoperation, timestamped, events, keep, track, entry, starts, message, status, global, note, defaults, needed, retrieved, tell, library, map, local, path, clone, possible, fastlaneservice, without, spaces, want, plug, options, consider, markdown, render, accordingly, fulldescnl, handle, plain, text, convert, line, breaks, fulldesc, video, featuregraphic, though, will, optimized, folder, containing, locale, dev, pre, shall, picked, well, reserved, test, development, variants, exception, opposite, definitely, repos, host, paid, mips, x86, unsigned, vnc, apkignore, purposes, architectures, noanalytics, v8a, apkmatch, obtained, depending, other, may, exist, initially, long, ago, outlined, look, instances, forgejo, gitea, removed, reason, right, before, actual, statistic, tools, appremoved, requires, root, otherwise, yes, requiresroot, overrides, config, beyond, size, limit, then, fit, else, archivepolicy, display, two, difference, that, override, itself, its, specify, while, instead, fallback, cannot, extracted, helps, recognize, looking, username, preferably, mentioned, opencollective, liberapay, addresses, project, donation, ideally, maintains, gets, automatically, synchronized, whenever, pulled, changes, weblate, crowdin, translation, bugs, feature, requests, make, suggestions, wiki, dedicated, even, web, homepage, authorwebsite, public, email, address, reached, something, happens, their, accounts, authoremail, nickname, chosen, legal, organisation, spdx, identifier, indicating, anti, features, might, ship, configured, details, why, antifeature, applies, english, locales, die, baut, verbindungen, und, auf, connects, nonfreenet, found, description, maintained, repositories, using, actively, order, expected, appear, 385ea9045e6ecfc3cccac1ec906f423677fe130ce9e7c19d9277c2b0aacc4026, allowedapksigningkeys, master, 2025, simplest, boosty, issues, aleksandr, iovlev, mit, writing, directory, package, aka, start, looks, traseapps, appid, packagename, repodata, builder, developers, preparing, recipes, known, establish, failed, rbs, links, sign, commits, replacing, proprietary, libraries, push, notifications, miscellaneous, running, mirror, inclusions, mirrors, schedules, badges, shields, assets, apis, signing, keys, browser, binary, transparency, logs, scans, initializing, search, free, world, under, threat, changing, way, install, device, keepandroidopen, org,
Text of the page (random words):
yaml metadata izzyondroid the free android world is under threat and izzyondroid with it google is changing the way you install apps on your device we need your help keepandroidopen org izzyondroid yaml metadata initializing search home about get started faq contributing documentation contact izzyondroid home about about security security apk scans binary transparency logs our repository browser reproducible builds signing keys resources resources apis assets badges shields schedules get started get started faq faq contributing contributing donating mirrors builders new app inclusions documentation documentation general general app inclusion policy fastlane running a mirror yaml metadata developer best practices developer best practices miscellaneous hints push notifications replacing proprietary libraries sign your commits useful links reproducible builds reproducible builds debug failed rbs establish an app for rb known verification builders preparing recipes rb hints for developers verification builder contact contact yaml metadata for each app in our repository there is a corresponding yaml file in the metadata directory which you can find in our repodata repository the apps package names aka packagename or appid defines the name of this file to start with an example here is how metadata com traseapps simplestnotes yml looks like categories writing license mit authorname aleksandr iovlev sourcecode https github com trase1 simplestnotes app issuetracker https github com trase1 simplestnotes app issues changelog https github com trase1 simplestnotes app releases donate https boosty to trase1 donate autoname simplest notes maintainernotes appadded 2025 07 24 method github release ghskippre 1 fastlane https github com trase1 simplestnotes app tree master fastlane metadata android fastlanefeatures shortdesc fulldescmd icon screenshots allowedapksigningkeys 385ea9045e6ecfc3cccac1ec906f423677fe130ce9e7c19d9277c2b0aacc4026 autoupdatemode version v v updatecheckmode tags as you can see app description and graphics are not in this place they are maintained in the apps repositories using fastlane format available and actively used fields in the yaml file are in the order they are expected to appear there antifeatures an object indicating any anti features an app might ship with a list of configured antifeatures can be found here details on why a given antifeature applies must be given at least in english en us additional locales are optional example antifeatures nonfreenet en us the app connects to youtube and google translate de die app baut verbindungen zu youtube und google translate auf categories mandatory a list of categories must be at least one but no more than 5 license mandatory one license in the format of an spdx identifier authorname mandatory the name of the author s usually a single name can be a nickname chosen legal name name of an organisation etc can be multiple names comma separated authoremail optional but strongly recommended a public email address the author s can be reached at e g if something happens to their git forge accounts authorwebsite optional homepage of the author s a single url only website optional a website with additional information on the app can be the app s wiki in the corresponding forge a dedicated website or even just a web page on the author s website sourcecode mandatory url to the app s git repository holding the source code of the app issuetracker optional but strongly recommended where people can file bugs feature requests make suggestions etc translation optional a link to where people can help translate the app usually a service like weblate or crowdin changelog optional a link to where changes for releases are listed usually the releases page of the corresponding forge donate optional an url to a donation page ideally the app s author maintains this information in a funding yml in the app s git repository so it gets automatically synchronized whenever a new release is pulled in bitcoin litecoin optional bitcoin litecoin addresses for donating to the project liberapay opencollective optional username at the corresponding service these should preferably go to above mentioned funding yml autoname name the display name of the app at least one of these two should be present the difference is that name would override what the app itself or the title txt in its fastlane tree specify while autoname instead used as a fallback in case the name cannot be extracted from the apk or app s fastlane metadata title txt and helps to recognize the app when looking at the yaml only archivepolicy overrides the repository s config value but just for this app usually only set if 3 releases of the app would go beyond the per app size limit of the repository see app inclusion policy it is then set to 2 if 2 releases would fit else to 1 requiresroot yes if the app requires root not present otherwise maintainernotes a mandatory object holding multiple fields appadded the date the app was added to our repo format yyyy mm dd appremoved the date an app was removed format yyyy mm dd followed by the reason of removal this is only set right before the actual removal and used by our statistic tools method method by which the apk is obtained depending on where the app is hosted values include codeberg release releases at codeberg or self hosted instances of forgejo gitea gitlab tags releases at gitlab gitlab com or self hosted github release github s releases page other values may exist with apps initially listed at izzyondroid long ago but are only used for historical reasons they are not outlined here as they are not available to new listings if you need to look them up you can find them in our schema definition apkmatch regex the file name should match in case we have multiple apk files for different purposes or architectures examples arm64 v8a noanalytics apk apkignore the opposite what definitely not to take useful e g when repos host multiple apps examples older vnc debug unsigned apk mips x86 apk paid ghskippre set to 0 i e ghskippre 0 if pre releases shall be picked up as well this is usually reserved for test development variants of apps which are the exception here fastlane url to the fastlane folder containing the changelogs e g https github com dev app fastlane metadata android a locale e g de de can be added if the changelogs are only available there and it is not en us fastlanefeatures comma separated list without any spaces of what we want to plug from fastlane available options include fulldesc shortdesc title video changelogs icon featuregraphic screenshots take the files as they are though graphics will be optimized on import fulldescnl handle full_description txt as plain text i e only convert line breaks to br fulldescmd consider full_description txt as markdown and render it accordingly fastlaneservice defaults to method above this is only needed when fastlane is to be retrieved from a different place than the apk to tell the import library how to map the url to a local path in the git clone of the app s repo possible values github gitlab codeberg note any global notes on the app status a timestamped list of events to keep track of each list entry starts with a date in yyyy mm dd format followed by the message vercodeoperation for cases where the per release changelogs are based on the versioncode of a different build architecture value must be enclosed in single quotes e g c 2000 subtract 2000 to versioncode of the apk to get the changelog file name e g 2021 21 for an arm64 build of a flutter app nosourcesince defines the last version source code was available for autoupdatemode string to match the version against with placeholders for versioncode c and versionname v not a regex example autoupdatemode version v v for a tag v1 2 3 pointing to versionname 1 2 3 info our framework currently only supports either c or v not both at the same time as the string is used as regex e g v v c could e g be written as v v d versioncode is always integer to go by versionname or v c to go by versioncode updatecheckmode how to check for updates tags check daily if there are new tags in the repo which have matching apk files static similar but only check once per month none disable no update check at all e g because the app s repo was archived or gone entirely these are the fields currently used and available for new listings more fields are kept in older yamls for historical reasons for a full list please refer to our schema definition back to top made with material for mkdocs
|
