boost-skill-cli 1.0.46__tar.gz → 1.0.48__tar.gz

{boost_skill_cli-1.0.46 → boost_skill_cli-1.0.48}/.gitignore

@@ -224,3 +224,6 @@ boost_cli/_version.py
 _bmad/
 _bmad-output/
 .claude/skills/bmad-*/
+
+# mutmut mutation-testing workspace (regenerated by `mutmut run`)
+mutants/

{boost_skill_cli-1.0.46 → boost_skill_cli-1.0.48}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.46
+Version: 1.0.48
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.46 → boost_skill_cli-1.0.48}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.46'
-__version_tuple__ = version_tuple = (1, 0, 46)
+__version__ = version = '1.0.48'
+__version_tuple__ = version_tuple = (1, 0, 48)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.46 → boost_skill_cli-1.0.48}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.46
+Version: 1.0.48
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.46 → boost_skill_cli-1.0.48}/docs/roadmap.html

@@ -116,7 +116,7 @@
       <div class="stat"><b>4</b><span>Shipped</span></div>
       <div class="stat"><b>3</b><span>Next up</span></div>
       <div class="stat"><b>4</b><span>Planned</span></div>
-      <div class="stat"><b>32</b><span>Loop finds</span></div>
+      <div class="stat"><b>48</b><span>Loop finds</span></div>
     </div>
   </section>
 
@@ -872,6 +872,285 @@
     </div>
   </section>
 
+  <!-- ============ COMPATIBILITY & INSTALL INTEGRITY ============ -->
+  <section class="block reveal" id="compat">
+    <div class="block-head">
+      <h2>Compatibility &amp; install integrity</h2>
+      <span class="count">// planned · free tooling to prove boost installs &amp; runs everywhere it claims</span>
+      <span class="rule"></span>
+    </div>
+    <div class="rgrid">
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Compat · Platform</span></div>
+        <h3>Windows in the CI matrix</h3>
+        <p>The test matrix runs macOS and Ubuntu only, so
+           <code>windows-latest</code> path separators, case-sensitivity and
+           console-encoding bugs ship uncaught to any Windows user. Adding one
+           matrix leg closes the biggest untested surface for a tool that promises
+           to work "everywhere your agent does".</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">untested OS</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Testing · Install</span></div>
+        <h3>Clean-env install smoke — pip &amp; <code>pipx</code></h3>
+        <p>Every gate runs against an editable <code>pip install -e .</code>, which
+           hides missing package-data, a broken entry point or an undeclared
+           dependency. A job that <code>pip install</code>s the built wheel into a
+           <em>fresh</em> venv (and <code>pipx install</code>s it) then runs
+           <code>boost --version</code> proves the artifact a user actually gets
+           works.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">tests the real artifact</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Testing · Deps</span></div>
+        <h3>Lowest-version resolution — <code>uv --resolution lowest-direct</code></h3>
+        <p>CI always installs the <em>newest</em> compatible dependencies, so the
+           lower bounds declared in <code>pyproject.toml</code> are never actually
+           exercised. Resolving and testing against the minimum versions catches
+           the "works here, breaks on the floor we advertise" class of bug.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">honours declared floors</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Compat · Python</span></div>
+        <h3>Pre-release Python canary — 3.14t free-threaded</h3>
+        <p>An allow-failure matrix leg on Python pre-releases and the free-threaded
+           (no-GIL) build gives early warning of breakage before users on new
+           interpreters hit it. Cheap insurance for a project that already targets
+           3.9&nbsp;→&nbsp;3.14 and can't afford a surprise on release day.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">continue-on-error</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Perf · Startup</span></div>
+        <h3>Startup &amp; import-time budget — <code>-X importtime</code></h3>
+        <p>For a CLI, cold-start latency <em>is</em> the UX — every command pays it.
+           A gate on <code>python -X importtime boost</code> catches the accidental
+           top-level import of a heavy module (the optional <code>[rag]</code> stack
+           is the obvious trap) and keeps common commands feeling instant.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">lazy-import guard</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Packaging</span></div>
+        <h3>Package-metadata validation — <code>twine check</code> + friends</h3>
+        <p>Before every publish, <code>twine check</code> confirms the long
+           description renders on PyPI, <code>check-wheel-contents</code> catches
+           stray or missing files, and <code>pyroma</code> scores the metadata
+           completeness. Stops a broken PyPI page or an empty wheel from reaching
+           users — the release path currently trusts the build blindly.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">pre-publish gate</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Repro</span></div>
+        <h3>Hash-pinned, reproducible toolchain — <code>uv.lock</code></h3>
+        <p>Pin the dev and CI toolchain with a hash-locked <code>uv.lock</code> (or
+           a hashed constraints file) so a yanked or compromised transitive
+           dependency can't silently change a build. The reproducibility layer that
+           complements Dependabot and <code>pip-audit</code> — same inputs, same
+           bytes, every run.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">supply-chain repro</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Testing · Infra</span></div>
+        <h3>One command, every env — <code>nox</code></h3>
+        <p>A <code>noxfile.py</code> makes the full lint / test / smoke / mutation
+           gate reproducible across 3.9&nbsp;→&nbsp;3.14 in isolated environments,
+           locally and in CI alike — so "green on my machine" and "green in CI"
+           finally mean the same thing, and a contributor can run the exact gate
+           before pushing.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★</b></span>
+          <span class="m">local == CI</span>
+        </div>
+      </article>
+
+    </div>
+  </section>
+
+  <!-- ============ SKILL-CONTENT TRUST & SAFETY ============ -->
+  <section class="block reveal" id="trust">
+    <div class="block-head">
+      <h2>Skill-content trust &amp; safety</h2>
+      <span class="count">// planned · boost's core threat model — the third-party skills it installs run inside an agent</span>
+      <span class="rule"></span>
+    </div>
+    <div class="rgrid">
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Content</span></div>
+        <h3>Prompt-injection scanning of skill Markdown</h3>
+        <p>The highest-signal gap: boost installs Markdown an agent then <em>executes</em>,
+           and nothing inspects that content. Scan skills for injection patterns —
+           <em>"ignore previous instructions"</em>, data-exfiltration prompts,
+           embedded <code>curl … | sh</code> — with free rule engines
+           (<code>semgrep</code> custom rules, <code>garak</code>/<code>llm-guard</code>
+           patterns) at tap and install time.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★★</b></span>
+          <span class="m">the core risk</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Integrity</span></div>
+        <h3>Integrity verification — <code>boost verify</code></h3>
+        <p>The lockfile already records a <code>sha256</code> per install via
+           <code>util.sha256_dir</code>, but nothing ever re-checks it. A
+           <code>verify</code> command (and a <code>doctor</code> gate) that
+           re-hashes installed skills and flags drift turns that stored digest into
+           actual tamper-detection — cheap, and built on machinery that already
+           exists.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">reuses sha256_dir</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Provenance</span></div>
+        <h3>Tap signing &amp; provenance — Sigstore / minisign</h3>
+        <p>A tap records its <code>commit</code> today but offers no cryptographic
+           proof the content came from its claimed publisher, so a hijacked mirror
+           can serve altered skills undetected. Verify a signature (Sigstore
+           keyless or <code>minisign</code>) before trusting a tap — free, and the
+           standard the wider ecosystem is converging on.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">keyless OIDC</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Registry</span></div>
+        <h3>Typosquat &amp; name-confusion detection</h3>
+        <p>The classic package-manager attack: a skill named one edit-distance from
+           a popular one, or a familiar name that quietly resolves to an unexpected
+           <code>owner/repo</code>. Flag near-duplicate names and owner mismatches
+           at search and install time so a user can't fat-finger their way into a
+           malicious skill.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">edit-distance guard</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Supply chain</span></div>
+        <h3>Update-diff before apply</h3>
+        <p><code>boost update</code> overwrites installed skills in place. Show a
+           content diff of what an upstream change alters — and require confirmation
+           for anything that touches executable-looking instructions — so a poisoned
+           update is <em>visible</em> instead of silent. The "review the diff" gate,
+           applied to skills.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>M</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">no silent overwrites</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Secrets</span></div>
+        <h3>Secret &amp; PII scanning of installed skills</h3>
+        <p>Point the round-2 secret scanners (<code>gitleaks</code>/<code>trufflehog</code>)
+           at <em>third-party</em> skill content, not just boost's own repo — catching
+           a skill that ships embedded credentials or, worse, one whose prompt
+           coaxes the agent into harvesting the user's. Same free tools, a different
+           and higher-stakes target.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">installed content</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Integrity</span></div>
+        <h3>Lockfile enforcement &amp; commit pinning</h3>
+        <p>Promote the recorded <code>sha256</code> from a note to a rule: refuse to
+           load a skill whose content has drifted from the lockfile, and let users
+           pin a skill to an exact commit. The enforcement layer that makes the
+           <code>verify</code> digest binding rather than advisory.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">pin to commit</span>
+        </div>
+      </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Security · Policy</span></div>
+        <h3>Capability manifest &amp; least-privilege policy</h3>
+        <p>Extend the existing <code>policy.py</code> so a skill declares the
+           capabilities it expects — network, shell, file scope — and the user's
+           policy allows or denies them. Turns install-time governance into
+           least-privilege for the instructions an agent is about to run, the
+           natural next step for a tool that already blocks installs by policy.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>L</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">builds on policy.py</span>
+        </div>
+      </article>
+
+    </div>
+  </section>
+
   <footer>
     <p>Maintained by the boost quality loop · themed with
        <a href="../style/boost.css">style/boost.css</a> ·