Smart-contract libraries
OpenZeppelin Contracts
Solidity implementations of common token, access-control and utility contracts.
Green — compatible use if you keep the notices
- SPDX or status
- MIT
- Confidence
- high
- Maintainer
- OpenZeppelin
- Runtime
- EVM, Solidity
- Repository
- OpenZeppelin/openzeppelin-contracts
GitHub licence API reported MIT on 2026-10-01. The project README also points at terms on openzeppelin.com/tos. Read both. Blockchain Lab has not audited this repository. A licence check is not a vulnerability scan, a dependency review, or a security audit.
Keep the copyright and permission notice with any substantial copy.
Reuse status
Research available. Reuse pending.
A permissive licence file was recorded. The reuse gates are unmet, so nothing from the repository is exported.
- Source class
- S3 candidate
- Commit
- Not pinned
- Source-derived demo
- Held
Available
- E0: Metadata
- E1: Research report
- E2: Citation bundle
- E3: Pattern blueprint
- E4: Test plan
- E5: Original scaffold
Not available
- E6: Source-derived demo pack — held
- E7: Full source bundle — held
- E8: Dataset export — held
- E9: Model-training pack — held
- E10: Production candidate pack — held
OpenZeppelin Contracts has a permissive file on record. That is not a cleared export. Non-commercial or demo use does not remove the licence duty. When in doubt, link — do not copy.
Use
- A reviewed token or access-control primitive on an EVM chain
- Starting from a maintained library instead of a pasted snippet
Do not use for
- A claim that a product is secure because it imports OpenZeppelin
- A securities offering, by itself
Risks
- Admin keys and upgrade proxies can override the token rules.
- An old release is not the current release.
Reviews required
- Security review of the contracts you actually deploy
- Legal review if the token represents a regulated claim
No source code is reproduced on this page. No commit SHA is published, because this release did not pin one.