The addon-datastore repository is a data pipeline of submitting, validating and transforming add-on data to views. These views are hosted on the NV Access server and are available in the NVDA Add-on Store.
Please note: the NVDA project including the Add-on Store has a Citizen and Contributor Code of Conduct. NV Access expects that all contributors and other community members will read and abide by the rules set out in this document while participating in the project or contributing add-ons.
Add-on authors who wish to have their add-on distributed through the Add-on Store should refer to the submission guide.
For an overview of the whole Add-on Store, read the design overview.
Ensuring that an add-on is safe to run is a difficult challenge that isn't addressed here. However, the metadata for a new submission (add-on release) can be confirmed to match its manifest description. Additionally, add-on file integrity can be enforced via a SHA256 checksum. The checksum allows NVDA to ensure that add-on releases are immutable.
- NV Access doesn't require a manual review of the add-on (code or user experience) itself before the add-on submission.
- NV Access manually maintains a list of approved submitters with permission to submit an add-on to the store
- You are welcome to review code / UX of add-ons and provide that feedback directly to add-on authors.
- The SHA256 checksum of the
.nvda-addonprevents undetected changes. - Add-ons should comply with the NVDA code of conduct.
Add-ons which are malicious or otherwise break the code of conduct can be removed by:
- Opening a pull request to remove the submitted add-on metadata
- Sending an email to [email protected]
This system does not restrict add-on authors from developing, publishing, and distributing an add-on outside this store.
NVDA will still allow local installation from a *.nvda-addon file.
The data hosted here is distributed under the ODC-PDDL license.
A plain language summary can be found here.