Lock and verify the full Python dependency closure

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, python

Research direction

Start by tracing the container and self-update bundle build definitions for both architectures, then find where Python requirements are installed and where dependency audits run in CI. Review the existing direct requirement pins and the prior work in #118 to understand supported Python and platform targets. Done means builds use the reviewed lock with hashes, CI audits the complete locked set, and the refresh workflow is documented.

Written by the indexing model from the issue text.

Description

enhancement

What to build

Make container and self-update bundle builds install a reproducible, integrity-checked Python dependency set, including transitives.

Context

Follow-up to #118. Direct requirements are pinned already; the audited direct-only dependency check did not assess a resolved transitive closure.

This follows the November 17 source audit. Treat it as a hardening/validation task, not a confirmed exploit report. Detailed audit evidence and validation limitations remain in the local audit report; report any confirmed vulnerability privately under SECURITY.md.

Acceptance criteria

  • Generate a reviewed lock with exact transitive versions and hashes for supported Python/platform targets.
  • Use the lock consistently for the container and both self-update bundle architectures.
  • Audit the complete locked dependency set in CI and document the refresh workflow.
  • Verify builds cannot silently resolve a different transitive package version.
  • Internal dependency/build change; wiki exempt.

Blocked by

None (can start independently). Coordinate with related issues without expanding their scope.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.