Terms of use
These terms cover pkg.futureblitz.dev, FutureBlitz’s package registry: its pages, its API, its
index at index.futureblitz.dev, and the archives at dl.futureblitz.dev. Making an account,
publishing a package, or using the registry from fb means agreeing to them, and to the
package policy and the code of conduct.
FutureBlitz itself
FutureBlitz, its compiler, its tools, and its standard library are open source under the Apache-2.0 license, in its repository. That license, not these terms, says what you can do with the software.
Your account
- You’re responsible for what’s done with your account and its API tokens. Keep your passkeys, recovery codes, and tokens to yourself, and revoke a token you think someone else has.
- One person, one account; a team is how several people own packages together.
- A username is yours while the account is. Don’t take one to pass yourself off as someone else.
- You can delete your account at any time from the dashboard. Its packages stay published, owned by their other owners, or by no one.
Publishing
- You may publish only what you have the right to publish, under the license its project.toml names, which has to be an SPDX license that lets others use it.
- Publishing a version gives the registry the right to store it, copy it, and serve it to anyone, for as long as it’s on the registry, along with its readme and docs. Everything else is your package’s license’s business.
- A published version is never replaced. You can yank it, and within 72 hours of publishing you can delete it if nothing depends on it; after that it stays, but for the reasons the package policy gives.
- The registry refuses an upload that fails its checks, and its admins delete the versions of a package that breaks the package policy, as that policy says.
Use of the registry
- Use it through
fb, the API, and these pages, within their limits: 30 publish attempts an hour per account, and the API’s rate limits per address. - Don’t try to disrupt it, get around its limits or checks, or reach what isn’t meant to be public, and don’t use it to store or serve files that aren’t packages.
- Mirroring the index and the archives is fine at a polite pace.
No warranty
The registry, its packages, and the software are provided as they are, without warranty of any kind. Packages are their publishers’, not the FutureBlitz project’s, which doesn’t review them before they’re published. To the extent the law allows, the FutureBlitz project isn’t liable for any damage from using the registry or anything on it.
Changes
When these terms change, this page changes.
Contact
Questions about these policies, and reports, go to a new issue on FutureBlitz's GitHub, which is public. A report that shouldn't be public goes to GitHub's private vulnerability reporting on FutureBlitz's repository, which only its maintainers see. The registry has no email address for them.