vyper
Pythonic Smart Contract Language for the EVM
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/vyperlang/vyper with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/vyperlang/vyper'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/vyperlang--vyper)HTML
<a href="/listings/vyperlang--vyper"><img src="/api/listings/vyperlang--vyper/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
uv (recommended)
Make sure you have `uv` installed
1. Clone this repo and `cd` into it 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference 3. Run `uv sync` 4. Run `source .venv/bin/activate` to activate the virtual environment 5. Run `vyper --version` to verify the setup 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
pip
Make sure you have `pip` (version 25.1 or above), `setuptools`, and `pytest` installed
1. Clone this repo and `cd` into it 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference 3. Run `python -m venv .venv` to create a virtual environment 4. Run `source .venv/bin/activate` to activate it 5. Run `make init` to install the main dependencies 6. Run `make dev-init` to install the dev dependencies 7. Run `vyper --version` to verify the setup 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 140 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="docs/_static/logo-dark.svg">
- <source media="(prefers-color-scheme: light)" srcset="docs/_static/logo-light.svg">
- <img height="100" src="docs/_static/logo-light.svg">
- </picture>
- [](https://github.com/vyperlang/vyper/actions/workflows/test.yml)
- [](http://docs.vyperlang.org/en/latest/?badge=latest "ReadTheDocs")
- [](https://discord.gg/6tw7PTM7C2)
- [](https://t.me/vyperlang)
- [](https://x.com/vyperlang)
- [](https://pypi.org/project/vyper "PyPI")
- [](https://hub.docker.com/r/vyperlang/vyper "DockerHub")
- [](https://codecov.io/gh/vyperlang/vyper "Codecov")
- [](https://github.com/vyperlang/vyper/actions/workflows/codeql.yml)
- # Getting Started
- See [Installing Vyper](http://docs.vyperlang.org/en/latest/installing-vyper.html) to install vyper.
- See [Tools and Resources](https://docs.vyperlang.org/en/latest/resources.html) for an additional list of framework and tools with vyper support.
- See [Documentation](http://docs.vyperlang.org/en/latest/index.html) for the documentation and overall design goals of the Vyper language.
- See [learn.vyperlang.org](https://learn.vyperlang.org/) for **learning Vyper by building a Pokémon game**.
- **Note: Vyper is constantly evolving, use with care and understand the risks associated with smart contract development.**
- # Installation
- See the [Vyper documentation](https://docs.vyperlang.org/en/latest/installing-vyper.html)
- for build instructions.
- # Compiling a contract
- To compile a contract, use:
- ```bash
- vyper your_file_name.vy
- ```
- ***generate bytecode***
- vyper -f bytecode file-name.vy > file-name.bin
- ***generate abi***
- vyper -f abi file-name.vy > file-name.abi
- There is also an [online compiler](https://vyper.online/) available you can use to experiment with
- the language and compile to ``bytecode`` and/or ``IR``.
- **Note: While the vyper version of the online compiler is updated on a regular basis it might
- be a bit behind the latest version found in the master branch of this repository.**
- # Contributing
- * See Issues tab, and feel free to submit your own issues
- * Add PRs if you discover a solution to an existing issue
- * For further discussions and questions, post in [Discussions](https://github.com/vyperlang/vyper/discussions) or talk to us on [Discord](https://discord.gg/6tw7PTM7C2)
- * For more information, see [Contributing](http://docs.vyperlang.org/en/latest/contributing.html)
- ## Contributing Code
- ### Setup
- #### uv (recommended)
- Make sure you have `uv` installed
- 1. Clone this repo and `cd` into it
- 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference
- 3. Run `uv sync`
- 4. Run `source .venv/bin/activate` to activate the virtual environment
- 5. Run `vyper --version` to verify the setup
- 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
- #### pip
- Make sure you have `pip` (version 25.1 or above), `setuptools`, and `pytest` installed
- 1. Clone this repo and `cd` into it
- 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference
- 3. Run `python -m venv .venv` to create a virtual environment
- 4. Run `source .venv/bin/activate` to activate it
- 5. Run `make init` to install the main dependencies
- 6. Run `make dev-init` to install the dev dependencies
- 7. Run `vyper --version` to verify the setup
- 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
- ### Commands
- * `vyper path/to/file.vy` to run your local copy of the compiler
- * `pytest` to test your changes
- Useful pytest flags:
- * `-x`: Fail test run on first test failure
- * `--instafail`: Show reason for test failure directly, instead of at the end of a test run
- * `--disable-warnings`: Hide warnings which occurred during tests
- * `make mypy` to type check your changes
- * `make lint` to check your files are correctly formatted (also runs mypy)
- ### Docker Setup
- Note: This is only useful for contributors, if you just want to use vyper, look [here](https://docs.vyperlang.org/en/latest/installing-vyper.html#docker).
- #### Build the image:
- `docker build . -t vyper -f Dockerfile`
- #### Check it runs:
- `docker run -v $(pwd):/code vyper --help`
- #### Run vyper:
- It works like `vyper` locally, with the difference that you should add `/code/` before the local path:
- `docker run -v $(pwd):/code vyper /code/<path to vy file>`
- Example:
- * `vyper -f abi_python examples/name_registry/name_registry.vy` becomes
- * `docker run -v $(pwd):/code vyper -f abi_python /code/examples/name_registry/name_registry.vy`
- ### Other Tips
- #### Checking performance
- To run a python performance profile (to find compiler perf hotspots):
- ```bash
- PYTHONPATH=. python -m cProfile -s tottime vyper/cli/vyper_compile.py "$@"
- ```
- The utility timer functions `timeit`, `profileit` and `cumtimeit` are available in `vyper/utils.py`.
- #### Getting call graph
- To get a call graph from a python profile, install `gprof2dot` and `xdot`, and run it like `gprof2dot -f pstats stats | xdot -`. (See https://stackoverflow.com/a/23164271/).
- #### Testing with hevm
- Install hevm by downloading it from the releases page (https://github.com/ethereum/hevm/releases/latest) and making sure it is in your PATH. hevm tests can be enabled with `--hevm` flag, and hevm tests can be selected with the `-m hevm` marker. For instance, `pytest -m "hevm" --hevm`.
- #### Fuzzing tests
- Fuzzing test are very slow, so they are not run by default.
- To run them, use `pytest -m "fuzzing"`.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.