Skip to content
Back to search

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vyperlang--vyper/badge.svg)](/listings/vyperlang--vyper)

HTML

<a href="/listings/vyperlang--vyper"><img src="/api/listings/vyperlang--vyper/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

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)

  1. <picture>
  2. <source media="(prefers-color-scheme: dark)" srcset="docs/_static/logo-dark.svg">
  3. <source media="(prefers-color-scheme: light)" srcset="docs/_static/logo-light.svg">
  4. <img height="100" src="docs/_static/logo-light.svg">
  5. </picture>
  6. [![Build Status](https://github.com/vyperlang/vyper/actions/workflows/test.yml/badge.svg)](https://github.com/vyperlang/vyper/actions/workflows/test.yml)
  7. [![Documentation Status](https://readthedocs.org/projects/vyper/badge/?version=latest)](http://docs.vyperlang.org/en/latest/?badge=latest "ReadTheDocs")
  8. [![Discord](https://img.shields.io/discord/969926564286459934.svg?label=%23vyper)](https://discord.gg/6tw7PTM7C2)
  9. [![Telegram](https://img.shields.io/badge/Vyperholics🐍-Telegram-blue)](https://t.me/vyperlang)
  10. [![Twitter](https://img.shields.io/twitter/follow/vyperlang)](https://x.com/vyperlang)
  11. [![PyPI](https://badge.fury.io/py/vyper.svg)](https://pypi.org/project/vyper "PyPI")
  12. [![Docker](https://img.shields.io/docker/cloud/build/vyperlang/vyper)](https://hub.docker.com/r/vyperlang/vyper "DockerHub")
  13. [![Coverage Status](https://codecov.io/gh/vyperlang/vyper/branch/master/graph/badge.svg)](https://codecov.io/gh/vyperlang/vyper "Codecov")
  14. [![Language grade: Python](https://github.com/vyperlang/vyper/workflows/CodeQL/badge.svg)](https://github.com/vyperlang/vyper/actions/workflows/codeql.yml)
  15. # Getting Started
  16. See [Installing Vyper](http://docs.vyperlang.org/en/latest/installing-vyper.html) to install vyper.
  17. See [Tools and Resources](https://docs.vyperlang.org/en/latest/resources.html) for an additional list of framework and tools with vyper support.
  18. See [Documentation](http://docs.vyperlang.org/en/latest/index.html) for the documentation and overall design goals of the Vyper language.
  19. See [learn.vyperlang.org](https://learn.vyperlang.org/) for **learning Vyper by building a Pokémon game**.
  20. **Note: Vyper is constantly evolving, use with care and understand the risks associated with smart contract development.**
  21. # Installation
  22. See the [Vyper documentation](https://docs.vyperlang.org/en/latest/installing-vyper.html)
  23. for build instructions.
  24. # Compiling a contract
  25. To compile a contract, use:
  26. ```bash
  27. vyper your_file_name.vy
  28. ```
  29. ***generate bytecode***
  30. vyper -f bytecode file-name.vy > file-name.bin
  31. ***generate abi***
  32. vyper -f abi file-name.vy > file-name.abi
  33. There is also an [online compiler](https://vyper.online/) available you can use to experiment with
  34. the language and compile to ``bytecode`` and/or ``IR``.
  35. **Note: While the vyper version of the online compiler is updated on a regular basis it might
  36. be a bit behind the latest version found in the master branch of this repository.**
  37. # Contributing
  38. * See Issues tab, and feel free to submit your own issues
  39. * Add PRs if you discover a solution to an existing issue
  40. * For further discussions and questions, post in [Discussions](https://github.com/vyperlang/vyper/discussions) or talk to us on [Discord](https://discord.gg/6tw7PTM7C2)
  41. * For more information, see [Contributing](http://docs.vyperlang.org/en/latest/contributing.html)
  42. ## Contributing Code
  43. ### Setup
  44. #### uv (recommended)
  45. Make sure you have `uv` installed
  46. 1. Clone this repo and `cd` into it
  47. 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference
  48. 3. Run `uv sync`
  49. 4. Run `source .venv/bin/activate` to activate the virtual environment
  50. 5. Run `vyper --version` to verify the setup
  51. 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
  52. #### pip
  53. Make sure you have `pip` (version 25.1 or above), `setuptools`, and `pytest` installed
  54. 1. Clone this repo and `cd` into it
  55. 2. Run `git fetch --tags git@github.com:vyperlang/vyper.git` to get the tags necessary for version inference
  56. 3. Run `python -m venv .venv` to create a virtual environment
  57. 4. Run `source .venv/bin/activate` to activate it
  58. 5. Run `make init` to install the main dependencies
  59. 6. Run `make dev-init` to install the dev dependencies
  60. 7. Run `vyper --version` to verify the setup
  61. 6. (optional) Run `git config blame.ignoreRevsFile .git-blame-ignore-revs` to improve `git blame`
  62. ### Commands
  63. * `vyper path/to/file.vy` to run your local copy of the compiler
  64. * `pytest` to test your changes
  65. Useful pytest flags:
  66. * `-x`: Fail test run on first test failure
  67. * `--instafail`: Show reason for test failure directly, instead of at the end of a test run
  68. * `--disable-warnings`: Hide warnings which occurred during tests
  69. * `make mypy` to type check your changes
  70. * `make lint` to check your files are correctly formatted (also runs mypy)
  71. ### Docker Setup
  72. 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).
  73. #### Build the image:
  74. `docker build . -t vyper -f Dockerfile`
  75. #### Check it runs:
  76. `docker run -v $(pwd):/code vyper --help`
  77. #### Run vyper:
  78. It works like `vyper` locally, with the difference that you should add `/code/` before the local path:
  79. `docker run -v $(pwd):/code vyper /code/<path to vy file>`
  80. Example:
  81. * `vyper -f abi_python examples/name_registry/name_registry.vy` becomes
  82. * `docker run -v $(pwd):/code vyper -f abi_python /code/examples/name_registry/name_registry.vy`
  83. ### Other Tips
  84. #### Checking performance
  85. To run a python performance profile (to find compiler perf hotspots):
  86. ```bash
  87. PYTHONPATH=. python -m cProfile -s tottime vyper/cli/vyper_compile.py "$@"
  88. ```
  89. The utility timer functions `timeit`, `profileit` and `cumtimeit` are available in `vyper/utils.py`.
  90. #### Getting call graph
  91. 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/).
  92. #### Testing with hevm
  93. 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`.
  94. #### Fuzzing tests
  95. Fuzzing test are very slow, so they are not run by default.
  96. To run them, use `pytest -m "fuzzing"`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.