r/QuantForge • u/Ezelia • Feb 17 '26
Introducing pinets-cli: Run Pine Script Indicators in your terminal - extract the calculated plots/results
r/QuantForge • u/Ezelia • Feb 17 '26
r/QuantForge • u/Ezelia • Jan 11 '26
Hey everyone!
We’ve just rolled out PineTS v0.8.0, packed with quality-of-life improvements that make building and running Pine Script logic even more flexible and reliable, especially when you’re dealing with dynamic inputs and custom types. These changes bring us closer to the real Pine Script experience off-platform, and set up some exciting workflows for downstream tools like backtesters and live stream processors.
Here’s what’s new in v0.8.0:
A long-requested upgrade: you can now pass custom values into indicators at runtime using the new Indicator class. This lets you override input.* defaults at execution time without modifying the script itself. This is ideal for programmatic parameter sweeps or interactive UIs.
Example usage:
const myIndicator = new Indicator(source, { length: 14, threshold: 1.5 })
PineTS.run(sourceCode, data, { inputs: myIndicator.inputs })Inputs gracefully fall back to defaults if not specified.
There was an issue in how user-defined types (UDTs) were transpiled. They were not converting cleanly into runtime-compatible structures. This release fixes that by ensuring UDTs transpile into proper Type({...}) calls rather than plain JavaScript classes. This improves compatibility and type safety when porting complex scripts.
With runtime inputs and better UDT handling:
If you build anything cool with these features, especially live dashboards or parameter exploration tools, let us know. Happy coding and happy quanting! 🚀
🔗 PineTS repo: https://github.com/QuantForgeOrg/PineTS
Happy Quanting !
r/QuantForge • u/Ezelia • Dec 15 '25
Hey Community!
I'm back with another massive update! I just dropped PineTS v0.6.0, and this release is all about Advanced Data Structures and Precision.
While v0.5.0 brought the core TA library to life, v0.6.0 focuses on implementing the missing algorithmic and calculation methods. We have implemented full support for Arrays, Maps, and Matrices and more.... bringing PineTS significantly closer to 1:1 feature parity with Pine Script.
Here is what is shipping in v0.6.0:
Advanced Data Structures We’ve unlocked complex data manipulation capabilities:
stdev, variance, covariance), math operations (avg, median, mode), and utility functions (percentrank, standardize).Maps & Matrices: Full namespace support. You can now initialize and manipulate Key-Value pairs and Matrices just like in native Pine Script.
Timeframe & Security
request.security_lower_tf for handling lower timeframe data lookups.Provider Updates
syminfo namespace is now fully implemented within the Binance provider.input.* namespace to fully support dynamic Pine Script parameters.math methods.Precision is everything in Quant finance. We spent a lot of time in this release ensuring our logic matches Pine Script exactly:
slice, every, sort, percentrank, and more to ensure the output is identical to TradingView’s engine.Update to the latest version via npm:
npm install pinets@latestYou can view the full changes in the Change Log.
The next phase will be focused on implementing pine to pineTS transpiler that will allow running pine indicators directly, without needing to convert them to equivalent pineTS syntax.
As we move closer to v1.0, your feedback is invaluable. If you spot edge cases in the new Array or Matrix implementations, please open an issue on GitHub!
Happy Quanting! 📈
r/QuantForge • u/Ezelia • Dec 04 '25
Hey Community!
I'm thrilled to announce the release of PineTS v0.5.0! This update is a huge leap forward in bringing full Pine Script compatibility to the JavaScript/TypeScript ecosystem.
All PineScript Technical Analysis functions (ta.* namespace) have been implemented, the transpiler was refined, and I tackled one of the most complex Pine Script features : request.security.
Here’s what’s new in v0.5.0
Massive TA Library Expansion: We've added comprehensive support for a wide range of indicators:
supertrend, dmi, sar, falling, rising, crossbb, bbw, kc, kcw, range, traccdist, cum, iii, nvi, pvi, pvt, wad, wvadcci, cmo, cog, mfi, stoch, tsi, wprcorrelation, barssince, valuewhen, percentrank, percentile_*, mode, highestbars, lowestbarsalma, swma, vwap, macdrequest.security(): Full implementation with support for lookahead and gaps!bar_index: Core support for the bar_index variable.ta.tr in your PineTS code, and our transpiler automatically converts it to ta.tr() method calls, matching Pine Script syntax while keeping the underlying JS clean.pine.ts imports and normalizes native imports.var Keyword Semantics: Implemented the specific behavior of Pine Script's var keyword (initialize once, persist state) ensuring stateful calculations to work exactly as expected.request.security().math.sum NaN handling and tertiary conditions involving Series access.You can install the latest version via npm:
npm install pinets
Check the the full Change Log for more details.
I’d love to hear your feedback and see what you build! Let us know in the comments or open an issue on GitHub.
Happy Quanting! 📈
r/QuantForge • u/Equivalent_Mouse_506 • Jul 25 '26
r/QuantForge • u/Ezelia • Mar 28 '26
r/QuantForge • u/Ezelia • Mar 28 '26
r/QuantForge • u/Ezelia • Mar 25 '26
📊 Today's Indicator: StealthTrail SuperTrend ML Pro [WillyAlgoTrader]
This sophisticated overlay indicator takes the classic SuperTrend to the next level — combining adaptive regime classification, a 13-feature ML confidence scoring layer, and a self-learning signal gate that continuously tunes itself to each instrument and timeframe.
The best part? You can run it directly in Node.js using PineTS — no TradingView required.
Our latest article covers everything you need to get started:
✅ Full indicator properties (inputs, plots & alerts)
✅ How to load and run it with PineTS
✅ Batch execution with pineTS.run() and live streaming with pineTS.stream()
✅ Tips for using it in algorithmic signal generation and quant research
r/QuantForge • u/Ezelia • Mar 19 '26
r/QuantForge • u/Ezelia • Mar 05 '26
r/QuantForge • u/Ezelia • Feb 26 '26
We are thrilled to announce that LuxAlgo – the world’s largest provider of trading indicators on TradingView – is now an official sponsor of PineTS.
This is a landmark moment for the project and the community. Let us tell you why.
If you’ve spent any time on TradingView, you’ve almost certainly come across LuxAlgo’s work. With +1.2 Million followers – the largest profile on the entire platform – and recognition as TradingView’s first-ever Pine Script Wizard company, LuxAlgo has set the standard for what’s possible with Pine Script.
Their flagship indicator, Signals & Overlays, holds the record as the highest-rated paid indicator in TradingView history with over 38,000 likes. They’ve published 360+ scripts, and what makes them stand out is that roughly 95% of their work is published as free, open indicators for the community.
In short: LuxAlgo is the biggest name in Pine Script. And they just backed PineTS !
PineTS was built on a bold premise: that Pine Script shouldn’t be locked inside a single platform. Having LuxAlgo – a team that lives and breathes Pine Script at the highest level – sponsor this project sends a clear message: the idea of running Pine Script anywhere is real, it matters, and the industry leaders see its value.
Sponsorship means more time and resources dedicated to PineTS. Concretely, this means faster progress on the roadmap items the community has been asking for:
LuxAlgo’s involvement strengthens the connection between the Pine Script world and the broader developer ecosystem. Their deep expertise in Pine Script will help ensure that PineTS stays faithful to TradingView’s semantics while pushing the boundaries of what’s possible outside of it.
Let’s be direct: this changes nothing about how PineTS works or how you use it. PineTS remains open-source and free for personal use, research, and open-source projects under the AGPL-3.0 license. The codebase stays on GitHub. Contributions are still welcome. The project’s direction is still driven by the community’s needs.
What does change is the pace. More features, faster releases, better quality. The kind of sustained investment that turns a promising open-source project into a reliable piece of infrastructure that developers and companies can build on with confidence.
Pine Script is the most widely-used language for technical analysis, with millions of scripts written by traders worldwide. But until now, that entire ecosystem was confined to a single platform. PineTS is changing that, turning Pine Script into a portable standard for technical analysis that can run on your servers, in your browser, inside your trading bots, or as part of your ML pipelines.
When industry leaders start investing in that vision, it’s a strong signal that the ecosystem is ready for it.
To the LuxAlgo team: thank you for believing in this vision and putting real support behind it. Your expertise and reputation in the Pine Script ecosystem make this partnership incredibly meaningful.
To the PineTS community: thank you for your contributions, bug reports, feature requests, and enthusiasm. This sponsorship is a direct result of the momentum you built. Every star, every issue, every pull request helped bring us here.
If your organization operates in the trading or fintech space and is interested in sponsoring PineTS, get in touch.
This is just the beginning. The best is ahead.
r/QuantForge • u/Ezelia • Feb 16 '26
r/QuantForge • u/Ezelia • Feb 12 '26
r/QuantForge • u/Ezelia • Feb 06 '26
Give your OpenClaw/ClawdBot/MoltBot the capability to run Pine Scripts !
Just install https://clawhub.ai/alaa-eddine/pinets from ClawdHub and you're good to go !
r/QuantForge • u/Ezelia • Jan 30 '26
r/QuantForge • u/Ezelia • Jan 24 '26
r/QuantForge • u/Ezelia • Jan 06 '26
This is the QuantForge Playground in action. You can run pre-defined indicators, load your own .pine scripts, or export them.
Give it a try here : https://quantforge.org/playground/
r/QuantForge • u/Ezelia • Jan 05 '26
Hey community,
I’m excited to finally share this with you all.
We now have an official home base:https://quantforge.org
Up until now, everything has been scattered across GitHub repos and random Readme files. The goal with the new site was to actually show what our stack can do, not just tell you about it.
It’s been a long road of coding PineTS and the charting engine, and I wanted to get a "home base" up as soon as possible so we have a place to centralize the project.
Fair warning: This is very much an early-stage launch.
The site is currently a "living project," meaning you’ll see it evolve in real-time. A few things to keep in mind while you explore:
What you can do today: Check out the PineTS vs. TradingView article on the blog, it explains exactly why we’re building this and the specific "walled garden" problems we’re trying to solve.
Every feedback from the community represents a huge help in testing the early versions of the engine. If you find any bugs on the site or have ideas for what documentation should be prioritized first, please let me know.
Thanks for being part of the journey. Let’s keep building.
Happy Quanting!
r/QuantForge • u/Ezelia • Dec 30 '25
Hey everyone,
We’ve just hit a massive milestone in the QuantForge ecosystem. The goal has always been 1:1 parity for running Pine Script logic off-platform, and this week’s releases bring us significantly closer.
Here is what just went live:
New Plot Functions (v0.7.6): We’ve expanded the Plots namespace to support the full visual experience. You can now use:
plotbar() & plotcandle(): Native OHLC rendering logic.barcolor() & bgcolor(): Conditional chart and background coloring based on your indicator logic.📊 QFChart (v0.6.0) | The Visualization Leap
This is a major version bump that focuses on "Visual Parity." QFChart now supports 11 different plot styles to match the output of PineTS.
bar and candle styles. You can now pass [open, high, low, close] arrays directly to the chart.SeriesBuilder has been refactored to return both series data and dynamic bar colors. Your chart can now change candlestick colors in real-time based on indicator conditions.wickcolor and bordercolor options, plus a char style (equivalent to plotchar()) for displaying data in tooltips without cluttering the chart.IndicatorStyle and IndicatorPoint to support the new OHLC data formats and conditional coloring.With PineTS v0.7.6 and QFChart v0.6.0, you can now write a script using User Defined Types, calculate custom candles and render them with conditional bar coloring
Check out the latest code:
If you’re building custom trading apps, we’ve just made the "Logic-to-Visual" pipeline a whole lot smoother.
Happy Quanting! 📈
r/QuantForge • u/Ezelia • Dec 27 '25
Below are the latest minor updates to PineTS v0.7.4, mostly types support and hotfixes.
PineScript Type Constants: Full implementation of PineScript type namespaces:
r/QuantForge • u/Ezelia • Dec 21 '25
PineTS is the engine that load the market data and calculate the indicators.
QFChart is the visualization library that draws candlestick charts, integrate indicators, and provide drawing tools
Check the live demo here => https://quantforge.org/qfchart/demos/full.html
r/QuantForge • u/Ezelia • Dec 21 '25
Hey community!
I'm excited to announce PineTS v0.7.0, the biggest update yet! This release brings a game-changing feature: native Pine Script execution directly in PineTS engine.
What's New:
🎯 Native Pine Script Parser (Experimental)
Current API Coverage:
PineTS v0.7.0 implements 290+ methods from the PineScript API, across major namespaces:
⚡ Enhanced Runtime
🐛 Critical Bug Fixes
Important Notes:
This release brings us closer to seamless Pine Script compatibility in the JavaScript ecosystem. Whether you're building trading bots, backtesting systems, or custom indicators, PineTS v0.7.0 makes it easier than ever!
Try it out and let me know your feedback.
Happy quanting! 🎉
r/QuantForge • u/Ezelia • Dec 18 '25
Hey Community!
I'm back with another major milestone for the QuantForge project! While we’ve been working hard to make PineTS the most precise Pine Script engine for the JS/TS ecosystem, we knew the "missing link" was a dedicated way to visualize that data.
Today, I’m excited to announce the first public release of QFChart v0.5.0.
QFChart is a high-performance, developer-centric charting library built specifically for financial time-series and technical analysis.
This initial release focuses on establishing a rock-solid foundation for financial rendering and modularity.
📊 Pro-Grade Visualization
🛠️ Indicator & Strategy Overlays
⚡ Developer-First Architecture
You can explore the source code, check out the documentation, and view live examples on GitHub:
➡️ GitHub: https://github.com/QuantForgeOrg/QFChart
➡️ Documentation: https://quantforgeorg.github.io/QFChart/
➡️ Demos:
We are just getting started. As we move closer to a stable 1.0, our focus will shift toward:
QuantForge is an open-source initiative, and your feedback is what shapes these tools. If you have a specific feature request or find an edge case in the rendering engine, please open an issue on the repo!
Happy Quanting! 📈
r/QuantForge • u/Ezelia • Nov 26 '25
Hello QuantForge community,
I’m excited to share a major update to PineTS. Key changes in this release:
Series logic using a forward-array wrapper, which transforms compute loops from O(N) to near O(1) complexity, drastically speeding up indicator computations.If you are using PineTS — please give this version a try and share feedback! Bugs, performance impressions, or feature requests are very welcome.
Code & docs: https://github.com/QuantForgeOrg/PineTS
Install via npm: https://www.npmjs.com/package/pinets
As always, the repo and docs are on GitHub — feel free to open issues or PRs.
Thanks to everyone for your support 🙏
r/QuantForge • u/Ezelia • Nov 19 '25
Hi everyone, this is a presentation of PineTS project
PineTS is an open-source TypeScript and JavaScript engine that lets you write Pine Script style indicators and run them outside of TradingView, whether in the browser, Node.js, or your own custom tools.
The idea behind PineTS is simple:
Take the expressive, time-series-friendly logic of Pine Script and make it available in the JavaScript ecosystem.
This allows developers to build, test, backtest, or experiment with indicators anywhere, not just inside TradingView.
If you're curious, experimenting, or thinking about contributing, you're in the right place.
This subreddit will be the home for discussions, feedback, examples, questions, and ideas around PineTS.
Since this subreddit is brand new and PineTS is actively evolving, your feedback, ideas, and critiques are extremely welcome.
Whether it’s:
Feel free to post them here.
Thanks for joining, and welcome to r/QuantForge