Security
What the code actually does
AddonLab is a small studio, so this page describes mechanisms instead of badges. Everything below is something the licensing and update server does today.
Where a protection is not in place, we say so further down rather than leave you to assume it.
Plugin packages
Never on the open web
Plugin archives are kept on a private disk outside the web root, and there is no symlink that would publish them. A direct request for a file path is refused, not served.
Signed links that expire
A download link is minted per release and signed over the product, the release and an expiry time. Alter any part of it and the link stops working. The default window is 30 minutes, and it comes from one configuration value rather than being fixed in the code.
Streamed, never exposed
The download route reads the file and streams it back through the application. The storage path never reaches your browser, so there is nothing to guess at or share.
A SHA-256 checksum per release
Every release carries a SHA-256 checksum computed from the archive when it is uploaded and stored alongside it, so a package can be checked against what we published.
Licenses and activations
No valid license, no package
The update check will tell a site that a newer version exists, but it only includes a download link when the license key sent with the request belongs to that product and is neither expired nor blocked. Otherwise the package field comes back empty.
Keys are random, not derived
A license key is 32 characters drawn from the cryptographic random source in PHP. Nothing about your account, your email or your order is encoded in it.
Rate limits per address
Activation and deactivation accept 60 requests a minute per IP address. Key validation, the update check and the product catalog accept 120. Guessing a key at scale is not practical against those limits.
A seat is matched by hash
Activations are matched on a SHA-256 hash of the hostname, and that hash is what enforces your seat count. The hostname and the URL are also stored in readable form so that you and our support can tell your sites apart. We are not going to claim the URL is hidden when it is not.
Freeing a seat deletes the record
Deactivating from inside WordPress removes the activation row outright rather than marking it inactive. There is no deactivate button in the customer portal yet, so until there is: deactivate from the plugin, or write to us and we free the seat.
Accounts and passwords
Hashed with bcrypt, never stored
Passwords pass through the framework hasher, bcrypt by default, at registration, at reset and when a member of staff sets one. The column holds a hash, the field is excluded from every serialised copy of your account, and nobody here can read your password or send it back to you.
Failed logins lock out
Five failed attempts against the same email and address pair trigger a timed lockout, and the countdown is shown on the form.
Reset links expire
A password reset token is good for 60 minutes, and a fresh one can be requested no more than once a minute.
Sessions stay on the server
Session data is kept in our database, not in the cookie. The cookie carries an identifier, is marked HTTP-only so page scripts cannot read it, and lapses after 120 minutes of inactivity.
What we hold about you
Your account
A name, an email address and a password hash. That is the whole of the account record.
No card data
There is no card number in our database and no column that could hold one. An order keeps a total, a currency, a status and the reference given to us by the payment provider. Nothing more.
What a plugin reports
When a plugin checks in it sends its slug and version, the WordPress and PHP versions, the locale, whether the install is a multisite, and the site URL with its hash. No license key, no account, no IP address, nothing about your visitors. Deactivating the plugin deletes the row.
Deleting the account cascades
You can delete your account from your profile. It asks for your current password, then removes the account together with its licenses, their activations and its orders. The database enforces that, so it does not depend on a cleanup job running.
Staff access
Two roles reach the panel
Only accounts marked admin or support can open the back office. Everyone else is refused, and the role is checked on every request rather than once at login.
The publishing API is off by default
The endpoints we use to publish releases from the command line refuse every request while no token is configured. When one is, the bearer token is compared in constant time so a wrong guess reveals nothing by how long it took.
Limits worth knowing
The useful half of a security page is the part that admits what is missing.
No badge to show you
We hold no third-party security accreditation and we will not name one we do not have. AddonLab is a small studio, and a badge would be a purchase rather than a fact about the code.
Only the password is hashed
Your name and email sit in ordinary database columns. Apart from the password hash and the site hash, we do not encrypt individual fields. If that matters for how you plan to use us, better that you know it now.
Nobody watches a screen overnight
There is no monitoring desk and no response time we are willing to promise. What exists is the rate limiting, the signed links and the role checks described above, plus a mailbox a person reads.
Staff actions are not logged yet
The table for recording what admin and support do is in place, but nothing writes to it so far. Treat staff actions as unrecorded until this page says otherwise.
On your side
Four habits that matter more here than anything we can do for you.
- Use a password you use nowhere else. We cannot tell you the old one, only help you set a new one.
- Treat a license key like a password. Anyone holding it can take a seat on your license.
- Keep WordPress and your plugins updated. The update server exists so that this stays one click.
- Back the site up before a major plugin update. Ordinary WordPress advice, and it applies to our plugins too.
Found a hole? Tell us.
Write to us with what you found and how to reproduce it. It reaches a person, not a queue. There is no bounty programme, and we would rather hear about it than not.