Open-source project
tapexyz/tape avatar
tapexyz/tape

Tape's six listed apps, a mobile script the table omits, and one dev port

an open media-sharing platform.

4,447 stars317 forksTypeScriptAGPL-3.0

At a glance

What is it?
The tape monorepo starts every workspace package from a single pnpm dev script, hands the frontend a port, and keeps a mobile app out of its own published app table. It is a readable source tree with a documentation layer that has fallen behind the code.
Who is it for?
Treat this repository as source worth reading rather than software ready to install. The six documented apps, the pnpm guard and the single dev port 4783 are enough to put a frontend in front of you, but storage, contract addresses, chain choice and hosting are all missing, so a fork means writing them yourself.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 176 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • tapexyz/tape4,447 ★ · -6
Star history
Repository2026-09-232026-11-14
tapexyz/tape4.5k4.4k

-6 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Six apps and eight packages share one root dev script

The repository is a pnpm monorepo, and its README splits the tree into six apps, named web, embed, cron, api, og and contracts, plus eight packages, named abis, config, constants, generic, server, browser, lens and ui. No entry point is singled out as the one that matters. Instead the root package.json hands every command to the whole workspace at once, and the same recursive, parallel shape repeats for start, build, codegen and typecheck.

json
    "dev": "pnpm -r --parallel run dev",
    "start": "pnpm -r --parallel run start",
    "build": "pnpm -r --parallel run build",
    "codegen": "pnpm -r --parallel run codegen",

Read as a working arrangement, one command covers every package instead of a chosen subset, so a checkout puts a frontend, an embed player, a scheduler, a backend, a meta tag generator and a contracts app in motion together. A root pnpm-workspace.yaml sits at the top level, and the README does not document which directories it declares as workspaces.

The root script reaches a mobile app the app table omits

Two root scripts narrow the workspace down to a single package, and both use names the README tables never spell out. One runs `pnpm --filter @tape.xyz/webv3 dev`; the other runs `pnpm --filter @tape.xyz/mobile expo:start`.

json
    "web": "pnpm --filter @tape.xyz/webv3 dev",
    "mobile": "pnpm --filter @tape.xyz/mobile expo:start",

The frontend row in the apps table is called web, with no mention of webv3 anywhere in the top level listing. The mobile filter has no row at all: six apps are named and none of them is mobile, and the README never says where that package lives or what it renders. Both filters therefore point at directories a reader has to guess, and a fresh clone gives no way to confirm the guess from documentation alone.

A single dev port is documented for six services at once

Install from the repository root, not from inside any one app:

bash
pnpm install

Then start the whole tree:

bash
pnpm dev

The address given after those two steps is `http://localhost:4783`, and 4783 is the only port in the README. Which service binds it is not written down. Since `pnpm dev` fans out across every workspace package, one URL is offered for a frontend, an embed player, background cron jobs, a backend application, a meta tag generator and permissionless signup contracts, with no port to service mapping and no note on whether the rest are reached through a proxy.

Media-sharing in one place, video-sharing in another

Two labels sit above this project and they do not match. The repository description field reads an open media-sharing platform, while the README's own line reads an open video-sharing platform and the root package.json repeats the narrower video wording. That narrower label fits an embed app described as an Embed Video Player, and it fits the Open graph meta tags generator that the og app exists to produce.

A third naming thread runs one level deeper. One row of the packages table gets an entry of its own, lens, described as everything related to lens indexer, inside a repository whose advertised homepage is tape.xyz. Nothing in the README connects those two names, and no configuration in the tree is documented that would tie an indexer to that domain. For anyone mapping services to a domain, the row is either a deliberate dependency or leftover naming, and the files decide rather than the prose.

An install started with npm is refused before anything downloads

Setup begins with a guard instead of a dependency step. The `preinstall` script in the root package.json is `npx only-allow pnpm`, the line that fails an install launched by another package manager before a single package is fetched. That refusal is why the install line in the README is `pnpm install` and never an npm equivalent, and it applies to everyone who clones the tree.

`@biomejs/biome` is pinned at 1.9.4 and husky is declared as ^9.1.7, and those two entries are the complete devDependency list. The `prepare` script runs husky so the git hooks in the top level `.husky` directory install themselves, and `biome:check` is `biome check. && pnpm typecheck`, which folds a full workspace type check into the lint command. A sibling `biome:fix` script writes corrections back, so a contributor can fix and verify in two commands without first learning the layout.

Signup runs through contracts, with no chain or address given

Two rows in the tables carry the signup path. The contracts app is permissionless signup contracts, and the abis package holds contract interfaces. Read together they say that account creation is meant to run without a gatekeeper, and then the documentation stops. No chain name, no contract address, no RPC endpoint and no deployment script appear anywhere in the README, and the root package.json defines eleven scripts without one that deploys anything.

Elsewhere the tree names its work just as briefly. Cron is cron jobs for background tasks and api is the backend application, with nothing said about the datastore behind either, and og is an Open graph meta tags generator with no statement of what it generates from. For a reader following a new account through to a stored video, the trail ends at folder names.

Storage, keys and hosting are absent from a project called open

A project described as open, with a homepage at tape.xyz, ships a README that reads as a pointer file. It does not document a database, an object store, a search index, environment variables, an environment file example, a container file or a deploy target. Nothing says where the backend and the contracts app read their secrets from, or how configuration reaches a running deployment, so the questions that decide whether this can run at all have no answer in the README.

What the README does offer points at people rather than machinery: a Discord community for open discussions on features and general questions, an X account, a status page at status.tape.xyz, and a contributing guide at `.github/CONTRIBUTING.md` that asks contributors to read it before opening an issue or a pull request because it holds the branching strategy and the local development environment notes. There is no API reference, no schema and no description of the data model.

Where the code and its documentation have drifted apart

Three mismatches define the present state of the tree. The apps table has no mobile row while the root package.json carries a `mobile` script aimed at `@tape.xyz/mobile`. The repository description says media-sharing and the README says video-sharing. And the root package.json still reads version 2.0.3-beta, the same value carried by the newest release tag dated 2024-07-25, even though the default branch took pushes as late as 2026-05-23.

Read together, those gaps point at a codebase that moved further than its prose did. Six apps, eight packages, the package reached by `expo:start`, an indexer row and a short README cannot all be current with each other. Anyone planning to run this locally has to reconcile the app list with the workspace filters first, and anyone planning to fork it has to supply the configuration, storage and hosting decisions the documentation leaves out.

Editorial conclusion

Treat this repository as source worth reading rather than software ready to install. The six documented apps, the pnpm guard and the single dev port 4783 are enough to put a frontend in front of you, but storage, contract addresses, chain choice and hosting are all missing, so a fork means writing them yourself. Reconcile the workspace filters against the app table before planning around either, and confirm that the package a mobile script targets exists in the tree at all, because its own documentation never lists it.

Frequently asked questions

What is tapexyz/tape and how is the repository organised?

The repository description calls it an open media-sharing platform, while the README calls it an open video-sharing platform. It is a pnpm monorepo holding six apps and eight packages, and it is started from the repository root with `pnpm install` followed by `pnpm dev`.

How do I start the tape codebase locally and where does it serve?

Run `pnpm install` at the repository root, then `pnpm dev`, and the README sends you to http://localhost:4783 afterwards. No other port is documented, and no service is mapped to that one, even though the dev script fans out across every workspace package.

Why does npm install fail when I clone tapexyz/tape?

The root package.json sets `preinstall` to `npx only-allow pnpm`, so an install launched by another package manager is turned away before dependencies are fetched. The install line in the README is `pnpm install` for that reason.

Does the tape monorepo include a mobile app?

The root package.json defines a `mobile` script that runs `pnpm --filter @tape.xyz/mobile expo:start`, but the README's apps table lists six apps and none of them is mobile. The README does not say where that package lives or what it renders.

What database or storage backend does tape use?

No database, object store, search index or set of environment variables is documented in the README. The apps table names a cron app for background tasks and an api app for the backend without adding any detail about either.

What licence is tapexyz/tape released under?

The README states that the tape codebase is open-sourced software licensed under AGPLv3, and the repository license field reads AGPL-3.0. Nothing else in the documentation adds terms for a fork.

Official sources

  1. License: AGPL-3.0
  2. Project website
  3. README
  4. Releases
  5. tapexyz/tape on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tapexyz-tape.svg)](https://hysenlabs.com/projects/tapexyz-tape)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tapexyz-tape.svg)](https://hysenlabs.com/projects/tapexyz-tape)

Was this useful?