@plasius/video 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,73 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on **[Keep a Changelog](https://keepachangelog.com/en/1.1.0/)**, and this project adheres to **[Semantic Versioning](https://semver.org/spec/v2.0.0.html)**.
+
+---
+
+## [Unreleased]
+
+- **Added**
+  - (placeholder)
+
+- **Changed**
+  - Added package-level GitHub CD publish workflow at `.github/workflows/cd.yml` for npm publication with provenance.
+  - Hardened publish sequence to run install/test/build before version tagging and npm publish.
+  - Replaced `audit:deps` from `depcheck` to `npm ls --all --omit=optional --omit=peer > /dev/null 2>&1 || true` to avoid deprecated dependency-chain risk.
+  - Updated CD test stage to execute `npm run test:coverage` and upload coverage to Codecov using OIDC in the release pipeline.
+  - Updated Vitest coverage reporters to include `lcov` output for Codecov ingestion.
+  - Made SBOM generation non-blocking in CD and only attest when `sbom.cdx.json` is present.
+
+- **Fixed**
+  - (placeholder)
+
+- **Security**
+  - Removed `depcheck` (and its `multimatch`/`minimatch` chain) from devDependencies to resolve reported high-severity audit findings.
+
+## [0.1.1] - 2026-02-21
+
+- **Added**
+  - Root-level standalone npm package scaffold in `/video` with package-local governance and legal docs.
+  - Demo runner script (`npm run demo:run`) with an executable sanity check at `demo/example.mjs`.
+
+- **Changed**
+  - Updated package metadata to point to the standalone `Plasius-LTD/video` repository.
+  - Updated TypeScript configuration to be package-local (removed monorepo-relative `extends`).
+  - Aligned toolchain dependency minimums with current `plasius-ltd-site` resolved requirements.
+
+- **Fixed**
+  - Corrected demo package labeling from `@plasius/ai` to `@plasius/video`.
+  - Corrected README links to reference package-local files.
+
+- **Security**
+  - Added package-local release/governance docs to support independent npm publishing workflows.
+
+## [0.1.0] - 2026-02-21
+
+- **Added**
+  - Initial standards-aligned package scaffold for `@plasius/video`.
+  - Added package-level `.nvmrc`, `.npmrc`, `legal/`, README, and changelog.
+
+- **Changed**
+  - (placeholder)
+
+- **Fixed**
+  - (placeholder)
+
+- **Security**
+  - (placeholder)
+
+---
+
+## Release process (maintainers)
+
+1. Update `CHANGELOG.md` under **Unreleased** with user-visible changes.
+2. Bump version in `package.json` following SemVer (major/minor/patch).
+3. Move entries from **Unreleased** to a new version section with the current date.
+4. Tag the release in Git (`vX.Y.Z`) and push tags.
+5. Publish to npm via GitHub CD pipeline.
+
+[Unreleased]: https://github.com/Plasius-LTD/video/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/Plasius-LTD/video/releases/tag/v0.1.1
+[0.1.0]: https://github.com/Plasius-LTD/video/releases/tag/v0.1.0

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct v2.1
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [conduct@plasius.co.uk](mailto:conduct@plasius.co.uk). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Enforcement Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence:** A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact:** A violation through a single incident or series of actions.
+
+**Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact:** A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence:** A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html)
+
+For answers to common questions about this code of conduct, see the [FAQ](https://www.contributor-covenant.org/faq)
+
+[homepage]: [https://www.contributor-covenant.org](https://www.contributor-covenant.org)
+
+If you have any questions or concerns regarding this Code of Conduct, please contact us at [conduct@plasius.co.uk](mailto:conduct@plasius.co.uk).

package/CONTRIBUTING.md

@@ -0,0 +1,201 @@
+# Contributing to @plasius/schema
+
+First off: thanks for taking the time to contribute!
+This document explains how to work on the project, how to propose changes, and what we expect in pull requests.
+
+> TL;DR
+>
+> - Be respectful and follow the Code of Conduct.
+> - Open an issue before large changes; small fixes can go straight to a PR.
+> - Write tests, keep coverage steady or improving.
+> - Use Conventional Commits.
+> - Don’t include real PII in code, issues, tests, or logs.
+
+---
+
+## Code of Conduct
+
+Participation in this project is governed by our **Code of Conduct** (see `CODE_OF_CONDUCT.md`). By participating, you agree to abide by it.
+
+## Licensing & CLA
+
+This project is open source (see `LICENSE`). To protect contributors and users, we require contributors to agree to our **Contributor License Agreement (CLA)** before we can merge PRs (see `legal/CLA.md`). You’ll be prompted automatically by the CLA bot on your first PR.
+
+> If your company has special legal needs, please contact the maintainers before sending large PRs.
+
+## Security
+
+**Never** report security issues in public issues or PRs. Instead, follow the process in `SECURITY.md`.
+
+---
+
+## What this project does
+
+`@plasius/schema` provides a small, strongly-typed schema library:
+
+- A fluent field builder (e.g. `field().string().required()`),
+- Built-in validators for common standards (ISO/RFC/OWASP, etc.),
+- PII annotations + redaction utilities,
+- Type inference for safe, consistent entities across projects.
+
+Contributions typically fall into: new validators, field builder features, type improvements, docs, and tooling quality.
+
+---
+
+## Getting started (local dev)
+
+### Prerequisites
+
+- Node.js (use the version specified in `.nvmrc` if present: `nvm use`).
+- npm (we use npm scripts in this repo).
+
+### Install
+
+```bash
+npm ci
+```
+
+### Build
+
+```bash
+npm run build
+```
+
+### Test
+
+```bash
+npm test
+# or, if using Vitest in watch mode
+npm run test:watch
+```
+
+### Lint & format
+
+```bash
+npm run lint
+npm run format
+```
+
+> Tip: set up your editor to run ESLint and Prettier on save.
+
+---
+
+## How to propose a change
+
+### 1) For bugs
+
+- Search existing issues first.
+- Open a new issue with:
+  - Clear title, steps to reproduce, expected vs actual behaviour,
+  - Minimal repro (code snippet or small repo),
+  - Environment info (OS, Node, package version).
+
+### 2) For features / refactors
+
+- For anything non-trivial, open an issue first and outline the proposal.
+- If the change affects public API or architecture, add an ADR draft (see `docs/adrs/`).
+
+### 3) Good first issues
+
+We label approachable tasks as **good first issue** and **help wanted**.
+
+---
+
+## Branch, commit, PR
+
+**Branching**
+
+- Fork or create a feature branch from `main`: `feat/xyz` or `fix/abc`.
+
+**Commit messages** (Conventional Commits)
+
+- `feat: add ISO-3166 alpha-3 validator`
+- `fix: correct RFC5322 email regex edge-case`
+- `docs: expand PII redaction examples`
+- `refactor: simplify field builder pipeline`
+- `test: add cases for currency code`
+- `chore: bump dev deps`
+
+**Pull Requests**
+
+- Keep PRs focused and small when possible.
+- Include tests for new/changed behaviour.
+- Update docs (README, JSDoc, ADRs) as needed.
+- Add a clear description of what & why, with before/after examples if useful.
+- Ensure CI is green (lint, build, tests).
+
+**PR checklist**
+
+- [ ] Title uses Conventional Commits
+- [ ] Tests added/updated
+- [ ] Lint passes (`npm run lint`)
+- [ ] Build passes (`npm run build`)
+- [ ] Docs updated (README/ADR/CHANGELOG if needed)
+- [ ] No real PII in code, tests, or logs
+
+---
+
+## Coding standards
+
+- **Language:** TypeScript with `strict` types.
+- **Style:** ESLint + Prettier.
+- **Tests:** Prefer Vitest (or Jest) + `@testing-library/*` for React-facing bits.
+- **Public API:** Aim for backward compatibility; use SemVer and mark breaking changes clearly (`feat!:` or `fix!:`).
+- **Performance:** Avoid excessive allocations in hot paths; prefer immutable patterns but mind GC pressure.
+- **Docs:** Add TSDoc comments for exported types/functions.
+
+### Validators
+
+- Add tests covering common/edge cases.
+- Cite the source/standard (e.g., ISO/RFC) in comments.
+- Keep regexes readable (use `x`/comments where possible) and benchmark if complex.
+
+### PII handling
+
+- Never include real PII in fixtures or examples.
+- Ensure redaction/cleaning functions operate **before** logging.
+- Add tests confirming no PII leaks to logs or thrown errors.
+
+---
+
+## Adding dependencies
+
+- Minimise runtime dependencies; prefer dev dependencies.
+- Justify any new runtime dependency in the PR description (size, security, maintenance).
+- Avoid transitive heavy deps unless critical.
+
+---
+
+## Versioning & releases
+
+- We follow **SemVer**.
+- Breaking changes require a major bump and migration notes.
+- Keep the `CHANGELOG.md` (or release notes) clear about user-facing changes.
+
+---
+
+## Documentation
+
+- Update `README.md` with new features or setup steps.
+- Add or update ADRs in `docs/adrs/` for architectural decisions.
+- Keep examples minimal, copy-pasteable, and tested when feasible.
+
+---
+
+## Maintainers’ process (overview)
+
+- Triage new issues weekly; label and assign.
+- Review PRs for correctness, tests, and docs.
+- Squash-merge with Conventional Commit titles.
+- Publish from CI when applicable.
+
+---
+
+## Questions
+
+If you have questions or want feedback before building:
+
+- Open a discussion or issue with a short proposal,
+- Or draft a PR early (mark as **Draft**) to get directional feedback.
+
+Thanks again for contributing 💛

package/CONTRIBUTORS.md

@@ -0,0 +1,27 @@
+# Contributing Guidelines
+
+Thank you for considering contributing to this project! We welcome contributions that improve the code, documentation, and overall project quality.
+
+## Getting Started
+
+- Fork the repository.
+- Create a feature branch from `main`.
+- Commit your changes with clear messages (we follow **Conventional Commits**).
+- Push your branch and open a Pull Request (PR).
+
+## Requirements
+
+- Write tests alongside code where possible.
+- Ensure all tests pass before submitting a PR.
+- Follow the repository’s coding style and linting rules.
+- Update documentation (README, ADRs, etc.) when making significant changes.
+- When making architectural changes, create a new ADR (Architecture Decision Record) that **succeeds** the previous one rather than modifying old ADRs. This preserves history and ensures decisions are traceable.
+- Use the [ADR template](./docs/adrs/adr-template.md) when writing new ADRs to ensure consistency.
+- Before your first contribution, sign the appropriate Contributor License Agreement (CLA). See [legal/CLA.md](legal/CLA.md) for details, then email the signed document to [contributors@plasius.co.uk](mailto:contributors@plasius.co.uk).
+
+## Communication
+
+- Use GitHub Issues for bugs and feature requests.
+- Pull Requests should describe the problem, solution, and trade-offs.
+
+We appreciate your support in making this project better!

package/LICENSE

@@ -0,0 +1,203 @@
+Copyright 2025 Plasius LTD
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+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.

package/README.md

@@ -0,0 +1,85 @@
+# @plasius/video
+
+[![npm version](https://img.shields.io/npm/v/@plasius/video.svg)](https://www.npmjs.com/package/@plasius/video)
+[![Build Status](https://img.shields.io/github/actions/workflow/status/Plasius-LTD/video/ci.yml?branch=main&label=build&style=flat)](https://github.com/Plasius-LTD/video/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](./LICENSE)
+[![Code of Conduct](https://img.shields.io/badge/code%20of%20conduct-yes-blue.svg)](./CODE_OF_CONDUCT.md)
+[![Security Policy](https://img.shields.io/badge/security%20policy-yes-orange.svg)](./SECURITY.md)
+[![Changelog](https://img.shields.io/badge/changelog-md-blue.svg)](./CHANGELOG.md)
+
+Video generation components and helpers for the Plasius ecosystem.
+
+Apache-2.0. ESM + CJS builds. TypeScript types included.
+
+---
+
+## Installation
+
+```bash
+npm install @plasius/video
+```
+
+---
+
+## Usage
+
+```ts
+import { videoPackageInfo } from "@plasius/video";
+
+console.log(videoPackageInfo.name, videoPackageInfo.version);
+```
+
+---
+
+## Node.js Version
+
+This project uses Node.js **24** by default. The version is pinned in the [`.nvmrc`](./.nvmrc) file.
+
+If you use [nvm](https://github.com/nvm-sh/nvm), run:
+
+```bash
+nvm use
+```
+
+---
+
+## Package Scope
+
+`@plasius/video` is intended to host reusable video generation interfaces and shared view-model logic used across Plasius applications.
+
+---
+
+## Development
+
+```bash
+npm install
+npm run build
+npm run test
+npm run demo:run
+```
+
+---
+
+## Publishing
+
+This package is published via GitHub CD only.
+
+1. Configure repository environment `production` with secret `NPM_TOKEN`.
+2. Run `.github/workflows/cd.yml` via **Actions -> CD (Publish to npm) -> Run workflow**.
+3. Select the version bump (`patch`, `minor`, `major`, or `none`) and optional pre-release id.
+
+---
+
+## Contributing
+
+We welcome contributions. See:
+
+- [Contributing Guide](./CONTRIBUTING.md)
+- [Code of Conduct](./CODE_OF_CONDUCT.md)
+- [Contributor License Agreement](./legal/CLA.md)
+
+---
+
+## License
+
+Licensed under the [Apache-2.0 License](./LICENSE).

package/SECURITY.md

@@ -0,0 +1,17 @@
+# Security Policy
+
+## Supported Versions
+
+We currently support the latest major version of this project. Older versions may not receive security updates.
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please report it privately by emailing us at [security@plasius.co.uk](mailto:security@plasius.co.uk). Please do not create a public issue for security-related matters.
+
+## Response Timeline
+
+We aim to acknowledge your report within 2 business days and to provide a more detailed response (including next steps and, if applicable, a timeline for a fix) within 7 business days.
+
+## Disclosure Policy
+
+We request that you give us the opportunity to address the vulnerability before publicly disclosing it. We will coordinate with you on public disclosure once a fix is available and deployed.

package/dist/index.cjs

@@ -0,0 +1,34 @@
+"use strict";
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __export = (target, all) => {
+  for (var name in all)
+    __defProp(target, name, { get: all[name], enumerable: true });
+};
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+
+// src/index.ts
+var index_exports = {};
+__export(index_exports, {
+  videoPackageInfo: () => videoPackageInfo
+});
+module.exports = __toCommonJS(index_exports);
+var videoPackageInfo = {
+  name: "@plasius/video",
+  version: "0.1.1"
+};
+// Annotate the CommonJS export names for ESM import in node:
+0 && (module.exports = {
+  videoPackageInfo
+});
+//# sourceMappingURL=index.cjs.map

package/dist/index.cjs.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/index.ts"],"sourcesContent":["export interface VideoPackageInfo {\n  name: \"@plasius/video\";\n  version: string;\n}\n\nexport const videoPackageInfo: VideoPackageInfo = {\n  name: \"@plasius/video\",\n  version: \"0.1.1\",\n};\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;AAKO,IAAM,mBAAqC;AAAA,EAChD,MAAM;AAAA,EACN,SAAS;AACX;","names":[]}

package/dist/index.d.cts

@@ -0,0 +1,7 @@
+interface VideoPackageInfo {
+    name: "@plasius/video";
+    version: string;
+}
+declare const videoPackageInfo: VideoPackageInfo;
+
+export { type VideoPackageInfo, videoPackageInfo };

package/dist/index.d.ts

@@ -0,0 +1,7 @@
+interface VideoPackageInfo {
+    name: "@plasius/video";
+    version: string;
+}
+declare const videoPackageInfo: VideoPackageInfo;
+
+export { type VideoPackageInfo, videoPackageInfo };

package/dist/index.js

@@ -0,0 +1,9 @@
+// src/index.ts
+var videoPackageInfo = {
+  name: "@plasius/video",
+  version: "0.1.1"
+};
+export {
+  videoPackageInfo
+};
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/index.ts"],"sourcesContent":["export interface VideoPackageInfo {\n  name: \"@plasius/video\";\n  version: string;\n}\n\nexport const videoPackageInfo: VideoPackageInfo = {\n  name: \"@plasius/video\",\n  version: \"0.1.1\",\n};\n"],"mappings":";AAKO,IAAM,mBAAqC;AAAA,EAChD,MAAM;AAAA,EACN,SAAS;AACX;","names":[]}

package/legal/CLA-REGISTRY.csv

@@ -0,0 +1 @@
+name,email,github,cla_type,date_signed

package/legal/CLA.md

@@ -0,0 +1,22 @@
+# Contributor License Agreements (CLA)
+
+To protect the intellectual property of this project and ensure clarity of rights, all contributors must sign a Contributor License Agreement (CLA) before their first contribution.
+
+## Which CLA should I sign?
+
+- **Individual CLA**: If you are contributing personally and not on behalf of an employer, sign the [Individual CLA](INDIVIDUAL_CLA.md).
+- **Corporate CLA**: If you are contributing as part of your work for a company, the company should sign the [Corporate CLA](CORPORATE_CLA.md).
+
+## How to sign
+
+1. Download the appropriate CLA file (Individual or Corporate).
+2. Fill in the required details, sign, and date it.
+3. Email a PDF copy of the signed document to **[contributors@plasius.co.uk](mailto:contributors@plasius.co.uk)** with subject: `CLA – Individual` or `CLA – Corporate`.
+
+## Registry
+
+All signed CLAs are logged internally in the CLA registry (`CLA-REGISTRY.csv`).
+
+## Questions?
+
+If you have questions about which CLA to sign or how the process works, email **[contributors@plasius.co.uk](mailto:contributors@plasius.co.uk)**.

package/legal/CORPORATE_CLA.md

@@ -0,0 +1,49 @@
+# Corporate Contributor License Agreement (CLA)
+
+## Purpose
+
+This agreement defines licensing terms for contributions made on behalf of a corporation to `@plasius/video`.
+
+## Agreement
+
+1. **Authority**  
+   The signer confirms they are authorized to enter this agreement on behalf of the corporation.
+
+2. **Copyright License Grant**  
+   The corporation grants a perpetual, worldwide, non-exclusive, royalty-free, irrevocable copyright license to use, reproduce, modify, sublicense, and distribute contributions.
+
+3. **Patent License Grant**  
+   The corporation grants a perpetual, worldwide, non-exclusive, royalty-free, irrevocable patent license for claims necessarily infringed by the contributed work.
+
+4. **Representations**  
+   The corporation represents contributions are original or properly licensed, and submission does not violate third-party rights.
+
+5. **No Revocation**  
+   This license is perpetual and non-revocable for accepted contributions.
+
+6. **Governing Law**  
+   This agreement is governed by the laws of the United Kingdom.
+
+---
+
+### @plasius/video
+
+**Corporation Legal Name:** _______________________________
+
+**Authorized Representative:** _____________________________
+
+**Title:** ________________________________________________
+
+**Email:** ________________________________________________
+
+**Date:** _________________________________________________
+
+**Signature:** ____________________________________________
+
+---
+
+## How to Sign
+
+- Fill in the fields above.
+- Sign and date the document.
+- Email a signed PDF to [contributors@plasius.co.uk](mailto:contributors@plasius.co.uk).

package/legal/INDIVIDUAL_CLA.md

@@ -0,0 +1,65 @@
+# Individual Contributor License Agreement (CLA)
+
+**Project:** @plasius/video (Plasius LTD)  
+**Version:** 1.0 - 2026-02-21  
+**Contact:** [contributors@plasius.co.uk](mailto:contributors@plasius.co.uk)
+
+---
+
+## 1. Definitions
+
+- **"You"** (or **"Contributor"**) means the individual signing this CLA and submitting Contributions to the Project.
+- **"Contribution"** means any original work of authorship, including code, documentation, data, designs, or feedback that You submit to the Project in any form.
+- **"Project"** means the @plasius/video package and related materials owned or managed by **Plasius LTD**.
+
+## 2. Copyright License Grant
+
+You grant to Plasius LTD a perpetual, worldwide, non-exclusive, transferable, sublicensable, royalty-free, irrevocable copyright license to use, reproduce, publicly display, publicly perform, modify, create derivative works of, and distribute Contributions in source and object form.
+
+## 3. Patent License Grant
+
+You grant to Plasius LTD and its sublicensees a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Contribution and derivative works thereof, limited to patent claims You own or control that would be infringed by Your Contribution.
+
+## 4. Moral Rights & Attribution
+
+To the maximum extent permitted by law, You waive and agree not to assert moral rights in or to the Contribution against Plasius LTD. Plasius LTD may, but is not required to, credit You.
+
+## 5. Representations & Warranties
+
+You represent that:
+
+1. You have sufficient rights to submit the Contribution and grant these licenses.
+2. Contributions do not include confidential information or trade secrets of third parties.
+3. To the best of Your knowledge, Contributions do not infringe third-party IP rights.
+4. If an employer may claim rights, You have written permission or are contributing outside employment scope.
+5. You will follow project policies (Code of Conduct, Security Policy) and applicable laws.
+
+## 6. Scope & Duration
+
+This CLA covers past and future Contributions to the Project unless revoked in writing. Revocation is not retroactive.
+
+## 7. Disclaimer
+
+THE CONTRIBUTION IS PROVIDED "AS IS" WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.
+
+## 8. Governing Law & Jurisdiction
+
+This CLA is governed by the laws of England and Wales, with exclusive jurisdiction in England and Wales.
+
+---
+
+## 9. Contributor Information & Signature
+
+**Full Name:** __________________________________________
+
+**Email:** ______________________________________________
+
+**GitHub Handle:** _______________________________________
+
+**Employer (if applicable):** _____________________________
+
+**Signature:** ___________________________________________
+
+**Date (YYYY-MM-DD):** ___________________________________
+
+Submission: Email signed copy to **[contributors@plasius.co.uk](mailto:contributors@plasius.co.uk)** with subject `CLA - Individual - <GitHubHandle>`.

package/package.json

@@ -0,0 +1,108 @@
+{
+  "name": "@plasius/video",
+  "version": "0.1.1",
+  "description": "Standalone npm package for video generation components and helpers for the Plasius ecosystem",
+  "type": "module",
+  "private": false,
+  "sideEffects": [
+    "*.css"
+  ],
+  "main": "./dist/index.cjs",
+  "module": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "files": [
+    "dist",
+    "src",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE",
+    "SECURITY.md",
+    "CODE_OF_CONDUCT.md",
+    "CONTRIBUTORS.md",
+    "CONTRIBUTING.md",
+    "legal"
+  ],
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.cjs"
+    },
+    "./package.json": "./package.json"
+  },
+  "scripts": {
+    "build": "tsup",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage",
+    "lint": "eslint .",
+    "prepare": "npm run build",
+    "clean": "rimraf dist",
+    "reset:clean": "rm -rf node_modules package-lock.json && npm run clean",
+    "audit:ts": "tsc --noEmit --pretty",
+    "audit:eslint": "eslint \"{src,apps,packages}/**/*.{ts,tsx}\" --max-warnings=0 --ext .ts,.tsx",
+    "audit:deps": "npm ls --all --omit=optional --omit=peer > /dev/null 2>&1 || true",
+    "audit:npm": "npm audit --audit-level=moderate || true",
+    "audit:test": "vitest run --coverage",
+    "audit:all": "npm-run-all -l audit:ts audit:eslint audit:deps audit:npm audit:test",
+    "demo:run": "npm run build && node demo/example.mjs"
+  },
+  "keywords": [
+    "video",
+    "video-generation",
+    "pixelverse",
+    "react",
+    "typescript",
+    "plasius"
+  ],
+  "author": "Plasius LTD <development@plasius.co.uk>",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Plasius-LTD/video.git"
+  },
+  "bugs": {
+    "url": "https://github.com/Plasius-LTD/video/issues"
+  },
+  "homepage": "https://github.com/Plasius-LTD/video#readme",
+  "peerDependencies": {
+    "react": "^19.1.0",
+    "react-dom": "^19.1.0"
+  },
+  "devDependencies": {
+    "@testing-library/react": "^16.3.0",
+    "@types/node": "^24.3.1",
+    "@types/react": "^19.2.14",
+    "@types/react-dom": "^19.2.3",
+    "@types/uuid": "^10.0.0",
+    "@typescript-eslint/eslint-plugin": "^7.0.0",
+    "@typescript-eslint/parser": "^6.15.0",
+    "@vitest/coverage-v8": "^4.0.18",
+    "ajv": "^6.12.6",
+    "eslint": "^10.0.1",
+    "npm-run-all": "^1.1.3",
+    "rimraf": "^6.0.1",
+    "tsup": "^8.5.0",
+    "tsx": "^4.21.0",
+    "typescript": "^5.9.3",
+    "vitest": "^3.2.4",
+    "zod": "^4.1.12"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "funding": [
+    {
+      "type": "patreon",
+      "url": "https://www.patreon.com/c/plasiusltd/membership"
+    },
+    {
+      "type": "github",
+      "url": "https://github.com/sponsors/Plasius-LTD"
+    }
+  ],
+  "engines": {
+    "node": ">=22.12"
+  },
+  "packageManager": "npm@11.4.2"
+}

package/src/index.ts

@@ -0,0 +1,9 @@
+export interface VideoPackageInfo {
+  name: "@plasius/video";
+  version: string;
+}
+
+export const videoPackageInfo: VideoPackageInfo = {
+  name: "@plasius/video",
+  version: "0.1.1",
+};