LEGAL
Terms of service.
Last updated 2 June 2026. Plain English: it is a beta, we provide no warranty, do not abuse the rate limits, do not resell, trust scores are signals not permission.
Acceptance
By using nipcode.xyz, the hosted API, the CLI, or any first-party Nipcode artifact, you accept these terms.
Beta status
Nipcode is in public beta. There is no SLA, no uptime guarantee, no compatibility promise on the API surface between minor versions. Breaking changes will be in the changelog.
License
The Nipcode source code is published under the MIT License. See LICENSE. Trust scores and decision output you receive from the API are yours to use, including commercially.
Fair use
- Rate limit: 60 requests per minute per API key, enforced on the server.
- Do not bulk-scrape source registries through our API. Call them directly if you need that.
- Do not run automated tests against our endpoints at sustained high rate. Use staging or a local mock.
Prohibited use
- Reselling the Nipcode API or the decision response as your own service
- Using Nipcode to attack, deanonymize, or harass any upstream package maintainer
- Circumventing rate limits, key scoping, or revocation
- Submitting deliberately misleading queries to manipulate the decision output
Trust scores are signals
A high trust score is not a guarantee that a package is safe. The install boundary always requires explicit user or host-policy approval. You are responsible for verifying any package before installing it. We disclaim liability for any damage resulting from a decision you made based on our output.
Intellectual property
"Nipcode" and the snowflake mark are project marks. See TRADEMARKS.md. Third-party registry names (npm, PyPI, crates, GitHub, etc.) belong to their owners. We are not affiliated with any of them.
Termination
We may revoke any API key at any time without notice if we detect abuse. You may delete your account at any time via the contact path in the privacy policy.
Changes
We may update these terms. Material changes will be announced via the GitHub repo and a note in the changelog before they take effect.
Contact
Open an issue at github.com/trynipcode/nipcode/issues.
