pflow-cli 0.8.0__tar.gz

pflow_cli-0.8.0/.gitignore

@@ -0,0 +1,190 @@
+docs/source
+
+# Trace analysis output
+scripts/analyze-trace/output/
+
+# From https://raw.githubusercontent.com/github/gitignore/main/Python.gitignore
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# Vscode config files
+.vscode/
+
+# Intellij IDEA
+.idea/
+
+# Cursor IDE config with API keys (keep rules, ignore sensitive config)
+.cursor/mcp.json
+
+.temp/
+.archive/
+
+# Added by Task Master AI
+# Logs
+logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+dev-debug.log
+# Dependency directories
+node_modules/
+# Environment variables
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
+# OS specific
+.DS_Store
+
+# Task files ?
+# .taskmaster/
+# tasks.json
+# tasks/
+
+# Scratchpads
+# scratchpads/
+
+# Claude data and logs
+.claude/data/
+
+# MCP servers
+.mcp-servers/
+
+# External docs
+.research-and-marketing/
+
+# User data directory (workflows, settings, traces)
+.pflow/
+
+# Demo recordings
+assets/demo.cast
+assets/README.md

pflow_cli-0.8.0/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+## v0.8.0 (2026-02-10)
+
+First public release on PyPI. Install with `uv tool install pflow-cli` or `pipx install pflow-cli`.
+
+- Changed PyPI package name to `pflow-cli` (`pflow` was already taken on PyPI).
+- Changed LLM node output to always return raw strings, preventing silent data loss when prose contains JSON code blocks. JSON fields remain accessible via dot notation (`${node.response.field}`).
+- Added `pflow skill` command group to publish workflows as AI agent skills for Claude Code, Cursor, Codex, and Copilot [#81](https://github.com/spinje/pflow/pull/81) ([Task 119](.taskmaster/tasks/task_119/task-review.md))
+- Added `pflow workflow history` command to view execution logs and previous inputs [#81](https://github.com/spinje/pflow/pull/81)
+- Added execution duration tracking (last run and running average) to workflow metadata.
+- Fixed CLI parameter parsing to respect declared input types, preventing numeric strings (e.g., Discord IDs) from being coerced to integers [#84](https://github.com/spinje/pflow/pull/84)
+- Fixed contradictory validation error messages when accessing outputs from batch processing nodes [#86](https://github.com/spinje/pflow/pull/86)
+- Fixed environment variable expansion in MCP server configurations to correctly resolve `${VAR}` in URLs and `settings.json` references.
+- Fixed code node runtime errors to display workflow file line numbers instead of code-block relative lines.
+- Improved workflow discovery matching accuracy by including node IDs and input names in the LLM context.
+- Improved markdown parser error messages to identify nested backticks as the likely cause of untagged code blocks.
+
+## v0.7.0 (2026-02-04)
+
+- Removed `--description` and `--generate-metadata` flags from `workflow save` command [#80](https://github.com/spinje/pflow/pull/80)
+- Removed legacy `${stdin}` shared store pattern in favor of explicit input routing [#73](https://github.com/spinje/pflow/pull/73)
+- Replaced JSON workflow format with a new Markdown-based format (`.pflow.md`) that treats workflows as executable documentation [#80](https://github.com/spinje/pflow/pull/80) ([Task 107](.taskmaster/tasks/task_107/task-review.md))
+- Added Python code node (`"type": "code"`) for in-process data transformation with native object inputs and AST-based type validation [#75](https://github.com/spinje/pflow/pull/75) ([Task 104](.taskmaster/tasks/task_104/task-review.md))
+- Added automatic stdin routing via `"stdin": true` input property to support Unix-style workflow chaining [#73](https://github.com/spinje/pflow/pull/73) ([Task 115](.taskmaster/tasks/task_115/task-review.md))
+- Added `disallowed_tools` parameter to `claude-code` node to block specific tools via allowlist patterns [#78](https://github.com/spinje/pflow/pull/78)
+- Fixed pre-execution validation logic to ensure `--validate-only` catches unknown node types without tracebacks [#67](https://github.com/spinje/pflow/pull/67)
+- Fixed template validation error when using nested dot-notation variables inside array brackets
+- Improved validation to detect and reject JSON strings containing embedded template variables [#69](https://github.com/spinje/pflow/pull/69)

pflow_cli-0.8.0/LICENSE

@@ -0,0 +1,70 @@
+# Functional Source License, Version 1.1, ALv2 Future License
+
+## Abbreviation
+
+FSL-1.1-ALv2
+
+## Notice
+
+Copyright 2026 Andreas Falcone
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under these Terms and Conditions, as indicated by our inclusion of these Terms and Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents, Redistribution and Trademark clauses below, we hereby grant you the right to use, copy, modify, create derivative works, publicly perform, publicly display and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use means making the Software available to others in a commercial product or service that:
+
+1. substitutes for the Software;
+2. substitutes for any other product or service we offer using the Software that exists as of the date we make the Software available; or
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+2. for non-commercial education;
+3. for non-commercial research; and
+4. in connection with professional services that you provide to a licensee using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our patents, the license grant above includes a license under our patents. If you make a claim against any party that the Software infringes or contributes to the infringement of any patent, then your patent license to the Software ends immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software, you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of the Software, you have no right under these Terms and Conditions to use our trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under the Apache License, Version 2.0 that is effective on the second anniversary of the date we make the Software available. On or after that date, you may use the Software under the Apache License, Version 2.0, in which case the following will apply:
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
+
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

pflow_cli-0.8.0/NOTICE

@@ -0,0 +1,45 @@
+pflow includes the following third-party software:
+
+llm (https://github.com/simonw/llm)
+Copyright (c) Simon Willison
+Licensed under Apache License 2.0
+
+llm-anthropic (https://github.com/simonw/llm-anthropic)
+Copyright (c) Simon Willison
+Licensed under Apache License 2.0
+
+anthropic (https://github.com/anthropics/anthropic-sdk-python)
+Copyright (c) Anthropic, PBC
+Licensed under MIT License
+
+click (https://github.com/pallets/click)
+Copyright (c) Pallets
+Licensed under BSD-3-Clause
+
+pydantic (https://github.com/pydantic/pydantic)
+Copyright (c) Samuel Colvin
+Licensed under MIT License
+
+jsonschema (https://github.com/python-jsonschema/jsonschema)
+Copyright (c) Julian Berman
+Licensed under MIT License
+
+mcp (https://github.com/modelcontextprotocol/python-sdk)
+Copyright (c) Anthropic, PBC
+Licensed under MIT License
+
+requests (https://github.com/psf/requests)
+Copyright (c) Kenneth Reitz
+Licensed under Apache License 2.0
+
+claude-agent-sdk (https://github.com/anthropics/claude-agent-sdk-python)
+Copyright (c) Anthropic, PBC
+Licensed under MIT License
+
+PocketFlow (https://github.com/The-Pocket/PocketFlow) - EMBEDDED COMPONENT
+Copyright (c) 2024 Zachary Huang
+Licensed under MIT License
+Embedded in this distribution under src/pflow/pocketflow/
+See src/pflow/pocketflow/LICENSE for full license text.
+
+For full license texts, see the respective project repositories.

pflow_cli-0.8.0/PKG-INFO

@@ -0,0 +1,315 @@
+Metadata-Version: 2.4
+Name: pflow-cli
+Version: 0.8.0
+Summary: Reusable CLI workflows from shell, LLM, HTTP, and MCP nodes
+Project-URL: Homepage, https://pflow.run
+Project-URL: Repository, https://github.com/spinje/pflow
+Project-URL: Documentation, https://docs.pflow.run
+Author-email: Andreas Falcone <andreas@pflow.run>
+License: # Functional Source License, Version 1.1, ALv2 Future License
+        
+        ## Abbreviation
+        
+        FSL-1.1-ALv2
+        
+        ## Notice
+        
+        Copyright 2026 Andreas Falcone
+        
+        ## Terms and Conditions
+        
+        ### Licensor ("We")
+        
+        The party offering the Software under these Terms and Conditions.
+        
+        ### The Software
+        
+        The "Software" is each version of the software that we make available under these Terms and Conditions, as indicated by our inclusion of these Terms and Conditions with the Software.
+        
+        ### License Grant
+        
+        Subject to your compliance with this License Grant and the Patents, Redistribution and Trademark clauses below, we hereby grant you the right to use, copy, modify, create derivative works, publicly perform, publicly display and redistribute the Software for any Permitted Purpose identified below.
+        
+        ### Permitted Purpose
+        
+        A Permitted Purpose is any purpose other than a Competing Use. A Competing Use means making the Software available to others in a commercial product or service that:
+        
+        1. substitutes for the Software;
+        2. substitutes for any other product or service we offer using the Software that exists as of the date we make the Software available; or
+        3. offers the same or substantially similar functionality as the Software.
+        
+        Permitted Purposes specifically include using the Software:
+        
+        1. for your internal use and access;
+        2. for non-commercial education;
+        3. for non-commercial research; and
+        4. in connection with professional services that you provide to a licensee using the Software in accordance with these Terms and Conditions.
+        
+        ### Patents
+        
+        To the extent your use for a Permitted Purpose would necessarily infringe our patents, the license grant above includes a license under our patents. If you make a claim against any party that the Software infringes or contributes to the infringement of any patent, then your patent license to the Software ends immediately.
+        
+        ### Redistribution
+        
+        The Terms and Conditions apply to all copies, modifications and derivatives of the Software.
+        
+        If you redistribute any copies, modifications or derivatives of the Software, you must include a copy of or a link to these Terms and Conditions and not remove any copyright notices provided in or with the Software.
+        
+        ### Disclaimer
+        
+        THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+        
+        IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+        
+        ### Trademarks
+        
+        Except for displaying the License Details and identifying us as the origin of the Software, you have no right under these Terms and Conditions to use our trademarks, trade names, service marks or product names.
+        
+        ## Grant of Future License
+        
+        We hereby irrevocably grant you an additional license to use the Software under the Apache License, Version 2.0 that is effective on the second anniversary of the date we make the Software available. On or after that date, you may use the Software under the Apache License, Version 2.0, in which case the following will apply:
+        
+        Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
+        
+        You may obtain a copy of the License at
+        
+        http://www.apache.org/licenses/LICENSE-2.0
+        
+        Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent-skill,ai-agent,automation,cli,llm,mcp,workflow
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: <4.0,>=3.10
+Requires-Dist: anthropic>=0.75
+Requires-Dist: claude-agent-sdk>=0.1.17
+Requires-Dist: click
+Requires-Dist: jsonschema>=4.20.0
+Requires-Dist: llm-anthropic==0.23
+Requires-Dist: llm-gemini>=0.28.1
+Requires-Dist: llm>=0.28
+Requires-Dist: mcp[cli]>=1.17.0
+Requires-Dist: pydantic
+Requires-Dist: pyyaml>=6.0.0
+Requires-Dist: requests>=2.32.5
+Description-Content-Type: text/markdown
+
+<table>
+  <tr>
+    <td><img src="assets/logo.png" alt="pflow" width="120"></td>
+    <td>
+      <h1>pflow</h1>
+      <p>
+        <a href="LICENSE"><img src="https://img.shields.io/badge/License-FSL--1.1--ALv2-blue.svg" alt="License"></a>
+        <a href="https://www.python.org/downloads/"><img src="https://img.shields.io/badge/python-3.10+-blue.svg" alt="Python 3.10+"></a>
+        <a href="https://github.com/spinje/pflow/actions/workflows/main.yml"><img src="https://github.com/spinje/pflow/actions/workflows/main.yml/badge.svg" alt="CI"></a>
+        <a href="https://docs.pflow.run"><img src="https://img.shields.io/badge/docs-docs.pflow.run-blue" alt="Docs"></a>
+      </p>
+    </td>
+  </tr>
+</table>
+
+pflow helps your agent build workflows it can reuse. It composes pre-built nodes — LLM calls, shell commands, HTTP requests, MCP tools — into a `.pflow.md` file. Save it, and it becomes a command that runs the same process every time.
+
+Saved workflows can be published as Skills with `pflow skill save`, making them available across Claude Code, Cursor, and other platforms.
+
+![pflow demo](assets/demo.gif)
+
+## What a workflow looks like
+
+I use pflow for my own releases. This workflow analyzes git commits since the last tag, classifies each one with an LLM (70 concurrent calls), and generates a CHANGELOG.md entry, a Mintlify docs update, and a release context file. It runs in about a minute.
+
+```bash
+pflow generate-changelog since_tag=v0.5.0
+```
+
+The whole thing is a `.pflow.md` file — markdown that renders as documentation on GitHub and executes as a CLI command. Here are a few steps from the [full workflow](examples/real-workflows/generate-changelog/workflow.pflow.md):
+
+````markdown
+### get-latest-tag
+
+Detect the most recent git tag to use as the changelog baseline.
+
+- type: shell
+
+```shell command
+git describe --tags --abbrev=0 2>/dev/null || echo 'v0.0.0'
+```
+
+### resolve-tag
+
+Pick the starting tag: either user-provided or auto-detected.
+
+- type: code
+- inputs:
+    since_tag: ${since_tag}
+    latest_tag: ${get-latest-tag.stdout}
+
+```python code
+since_tag: str
+latest_tag: str
+
+result: str = since_tag.strip() if since_tag.strip() else latest_tag.strip()
+```
+
+### analyze-commits
+
+Classify each commit as user-facing or internal. Runs in parallel.
+
+- type: llm
+
+```yaml batch
+items: ${get-commits-enriched.result}
+parallel: true
+max_concurrent: 70
+```
+
+### notify-slack
+
+Post the release summary to Slack.
+
+- type: mcp-composio-slack-SLACK_SEND_MESSAGE
+- channel: ${slack_channel}
+- markdown_text: ${create-summary.result}
+````
+
+Data flows between steps through template variables — `${get-latest-tag.stdout}` feeds one step's output into the next.
+
+Four node types in one workflow: a shell command, inline Python, 70 parallel LLM calls, and a Slack message via MCP in three lines.
+
+More examples: [release announcements](examples/real-workflows/release-announcements/), [webpage to markdown](examples/real-workflows/webpage-to-markdown/)
+
+Once saved, this runs the same way every time — same steps, same order, same data flow between them.
+
+## How your agent uses pflow
+
+pflow has 8 node types: `shell`, `code` (Python), `http`, file operations, `llm` calls, `mcp` tools, and a `claude-code` node for delegating to another agent.
+
+Before anything runs, validation catches errors — wrong template references, missing inputs, type mismatches. Your agent handles the whole lifecycle:
+
+```bash
+# Check if a workflow already exists
+pflow workflow discover "generate changelog from git history"
+
+# Nothing fits — get a step-by-step creation guide
+pflow instructions create
+
+# Find building blocks for the workflow
+pflow registry discover "analyze git commits, classify with llm, post to slack"
+
+# Build, run, iterate (validation runs automatically)
+pflow workflow.pflow.md since_tag=v0.5.0
+
+# Save to your library
+pflow workflow save ./workflow.pflow.md --name generate-changelog
+
+# Publish frequently-used workflows as Skills
+pflow skill save generate-changelog
+```
+
+Workflows can call other workflows — the changelog you build today becomes a building block for a release workflow tomorrow.
+
+```bash
+# JSON output works with standard tools
+pflow --output-format json generate-changelog \
+  | jq -r '.result.version' | xargs git tag
+
+# Chain workflows together
+pflow -p generate-changelog | pflow -p release-announcements
+
+# Schedule workflows like any command
+0 9 * * MON pflow generate-changelog
+```
+
+## Built for agents
+
+When something goes wrong, pflow tells the agent what to do:
+
+```
+✗ Static validation failed:
+  • Node 'fetch-data' (type: http) does not output 'email'
+
+Available outputs from 'fetch-data':
+  ✓ ${fetch-data.response} (dict|str)
+  ✓ ${fetch-data.status_code} (int)
+  ✓ ${fetch-data.response_headers} (dict)
+  ✓ ${fetch-data.response_time} (float)
+  ✓ ${fetch-data.error} (str)
+
+Tip: Try using ${fetch-data.response} instead
+```
+
+The agent sees what went wrong, sees every available output with its type, and gets a suggested fix. No stack traces, no guessing. ([source](src/pflow/runtime/template_validator.py))
+
+I develop pflow by having agents build workflows and identifying where they get stuck. These error messages are a direct result.
+
+pflow is CLI-first because agents in Claude Code, Cursor, and similar tools always have bash. No MCP configuration needed — just run commands. (MCP server mode is available too if you need it.)
+
+## Honest scope
+
+pflow is for workflows where you know the steps — tasks your agent figured out once and you want to capture. If you're exploring or need your agent to adapt on the fly, let it. pflow captures the path after you've found it.
+
+## Getting started
+
+Requires Python 3.10+, macOS or Linux (Windows is untested). See the [quickstart](https://docs.pflow.run/quickstart) for API key setup and detailed configuration.
+
+```bash
+# Recommended
+uv tool install pflow-cli
+
+# Or with pipx
+pipx install pflow-cli
+
+# Or with pip
+pip install pflow-cli
+
+# Verify
+pflow --version
+```
+
+Tell your agent to run `pflow instructions usage` — it gets everything it needs to discover, run, and build workflows.
+
+Or configure pflow as an MCP server for environments without terminal access:
+
+```json
+{
+  "mcpServers": {
+    "pflow": {
+      "command": "pflow",
+      "args": ["mcp", "serve"]
+    }
+  }
+}
+```
+
+Full documentation at [docs.pflow.run](https://docs.pflow.run).
+
+## I want your feedback
+
+I've been building pflow since mid-2025. The thesis I'm testing: agents are more effective when they can compose known building blocks into reusable workflows, rather than writing code from scratch each time.
+
+I might be wrong. Try it and tell me:
+
+- Is the `.pflow.md` format helpful, or would you rather just read/write Python?
+- After trying it — would you rather just let your agent handle the whole task from scratch each time? Write scripts? Use some other framework?
+- What's the first workflow you'd build?
+
+Open a [discussion](https://github.com/spinje/pflow/discussions) or file an [issue](https://github.com/spinje/pflow/issues).
+
+Or get started → [Get started](https://docs.pflow.run/quickstart)
+
+## License
+
+[Functional Source License (FSL-1.1-ALv2)](LICENSE) — free for all use except offering pflow as a competing cloud hosted service. Becomes Apache-2.0 after 2 years.