Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Lumibot is a backtesting and trading library for stocks, options, crypto, futures and more. It is made so that the same code you use for backtesting can be used for live trading, making it easy to transition from backtesting to live trading. Lumibot is a highly flexible library that allows you to create your own strategies and indicators, and backtest them on historical data. It is also highly optimized for speed, so you can backtest your strategies quickly and efficiently.
IMPORTANT: This library requires data for backtesting. The recommended data source is Polygon.io (a free tier is available too). Please click the link to give us credit for the sale, it helps support this project. You can use the coupon code 'LUMI10' for 10% off.
To get started with Lumibot, you can check out our documentation below.
Check out the documentation for the project here: 👉 http://lumibot.lumiwealth.com/ 👈
Our blog has lots of example strategies and shows you how to run a bot using LumiBot. Check the blog out here:
To run a backtest, you can use the following code snippet:
python -m lumibot.example_strategies.stock_buy_and_hold
We made a small example strategy to show you how to use Lumibot in this GitHub repository: Example Algorithm GitHub
To run this example strategy, click on the Deploy to Render
button below to deploy the strategy to Render (our recommendation). You can also run the strategy on Repl.it by clicking on the Run on Repl.it
button below.
For more information on this example strategy, you can check out the README in the example strategy repository here: Example Algorithm
If you want to contribute to Lumibot, you can check how to get started below. We are always looking for contributors to help us out!
Here's a video to help you get started with contributing to Lumibot: Watch The Video
Steps to contribute:
pip install -r requirements_dev.txt
to install the developer dependenciespip install -e .
pytest
to make sure all the tests passWe use pytest for our testing framework. Some tests require API keys to be in a .env
file in the root directory. To run the tests, you can run the following command:
pytest
To run an individual test file, you can run the following command:
pytest tests/test_asset.py
To show code coverage, you can run the following command:
coverage run; coverage report; coverage html
This will show you the code coverage in the terminal and also create a folder called "htmlcov" which will have a file called "index.html". You can open this file in your browser to see the code coverage in a more readable format.
If you don't want to keep typing out the command, you can add it as an alias in bash. To do this, you can run the following command:
alias cover='coverage run; coverage report; coverage html'
This will now allow you to run the command by just typing "cover" in the terminal.
cover
If you want to also add it to your .bashrc file. You can do this by running the following command:
echo "alias cover='coverage run; coverage report; coverage html'" >> ~/.bashrc
If you are on Windows, you can add an alias by running the following command:
Add to your PowerShell Profile: (profile.ps1)
function cover {
coverage run
coverage report
coverage html
}
To set up in VS Code for debugging, you can add the following to your launch.json file under "configurations". This will allow you to go into "Run and Debug" and run the tests from there, with breakpoints and everything.
NOTE: You may need to change args to the path of your tests folder.
{
"name": "Python: Pytest",
"type": "python",
"request": "launch",
"module": "pytest",
"args": [
"lumibot/tests"
],
"console": "integratedTerminal",
}
Here's an example of an actual launch.json file:
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Pytest",
"type": "python",
"request": "launch",
"module": "pytest",
"args": [
"lumibot/tests"
],
"console": "integratedTerminal",
}
]
}
This table points out some of the differences between the data sources we use in Lumibot. These refer to the data returned in a Bars entity that is returned from calls to get_historical_prices.
data_source | type | OHLCV | split adjusted | dividends | returns | dividend adjusted returns |
---|---|---|---|---|---|---|
yahoo | stock | Yes | Yes | Yes | Yes | Yes |
alpaca | stock | Yes | Yes | No | Yes | No |
polygon | stock | Yes | Yes | No | Yes | No |
Tradier | stock | Yes | Yes | No | Yes | No |
Pandas* | stock | Yes | Yes | Yes | Yes | Yes |
*Pandas is not a data source per se, but it can load csv files in the same format as Yahoo dataframes, which can contain dividends.
Making a new branch and pulling from main:
git checkout -b my-feature
git fetch origin
git merge origin/dev
Committing work to you feature branch:
git add .
git commit -m "my changes"
git push -u origin my-feature
If work on main progressed while you were in another branch, this is how you rebase it into your branch. Note that since you've rebased your local branch, you'll need to force push your changes to update the remote branch. The --force-with-lease option is a safer alternative to --force as it will abort the push if there are any new commits on the remote that you haven't incorporated into your local branch
git checkout dev
git fetch origin
git merge origin/dev
git checkout my-feature
git rebase dev
git checkout my-feature
git push --force-with-lease origin my-feature
When ready to merge the branch into main, go into github, create a pull request, and await review. When your PR is approved it will automatically be merged into the dev branch remotely. Now, you can delete your local branch and the remote branch.
git checkout dev
git fetch origin
git merge origin/dev
git branch -D my-feature
git push origin --delete my-feature
If you want to learn more about Lumibot or Algorithmic Trading then you will love out communities! You can join us on Discord.
Join us on Discord: https://discord.gg/TmMsJCKY3T
If you need extra help building your algorithm, we have courses to help you out.
For our Algorithmic Trading course: https://lumiwealth.com/algorithmic-trading-landing-page
For our Machine Learning for Trading course: https://www.lumiwealth.com/product-category/machine-learning-purchase/
For our Options Trading course: https://www.lumiwealth.com/product-category/options-trading-purchase/
This library is covered by the MIT license for open sourced software which can be found here: https://github.com/Lumiwealth/lumibot/blob/master/LICENSE
FAQs
Backtesting and Trading Library, Made by Lumiwealth
We found that lumibot demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.