Pipfile.lock Dependency Parser
Paste a Pipfile.lock and get its pinned dependencies back as Pipfile entries and as requirements.txt lines, each with a copy button. Reads both default and develop sections, and skips entries with no pinned version rather than emitting broken pins. Handy for getting a requirements.txt out of a Pipenv project without installing Pipenv. Runs fully client-side. Imported Claude artifact. Source: https://github.com/simonw/tools (pipfile.html, Apache-2.0).
Name your fork
This clones the app's prompt and source into your account as a new unlisted app. You can edit and publish it from your dashboard.
Details
View source prompt + release files — fork-enabled apps share their full source
System prompt (SKILL.md)
---
name: pipfile-lock-parser
description: Paste a Pipfile.lock and get its pinned dependencies back as Pipfile entries or as requirements.txt.
metadata:
tags:
- artifact-import
- dev-tools
source_url: https://tools.simonwillison.net/pipfile
github_repo_url: https://github.com/simonw/tools
---
# Pipfile.lock Dependency Parser
An imported Claude artifact. Paste a Pipfile.lock, hit Parse, and every pinned
package comes back in two forms side by side - Pipfile-style entries and plain
requirements.txt lines - each with its own copy button.
It reads both the `default` and `develop` sections, and only emits packages
that actually carry a pinned version, so entries resolved from a VCS ref or a
local path are skipped rather than being written out as broken pins.
Useful when you need a requirements.txt from a Pipenv project without
installing Pipenv, or when you want the exact resolved versions in a form you
can paste into an issue or a Dockerfile.
Parsing happens in the page. Nothing is uploaded, no model is called, and
nothing is metered.
Release files (files)
Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.