dsh-plugin-inspector 0.2.1 → 0.4.0

package/lib/types/checks/tier-b.d.ts

@@ -14,6 +14,26 @@
  */
 import type { Finding } from '../model.ts';
 import type { CheckInput } from './input.ts';
+/** One filesystem location that holds credentials, and how it is spelled. */
+export interface CredentialPath {
+    readonly id: string;
+    /** Pattern source, matched case-insensitively anywhere in a string literal. */
+    readonly pattern: string;
+}
+/**
+ * Filesystem locations that hold credentials.
+ *
+ * A table rather than one regular expression so each location can be pinned by
+ * name: `tests/unit/rule-tables.spec.ts` iterates this export, and a location
+ * added without a fixture fails there.
+ */
+export declare const CREDENTIAL_PATHS: readonly CredentialPath[];
+/**
+ * Whether a string names a location that holds credentials.
+ * @param text - the literal text of a string in shipped source.
+ * @returns true when it names one of {@link CREDENTIAL_PATHS}.
+ */
+export declare function matchesCredentialPath(text: string): boolean;
 /**
  * Run every Tier B check.
  * @param input - the decoded package.

package/lib/types/cordis-yaml.d.ts

@@ -82,10 +82,23 @@ export interface PatchDocument {
      * means the layer was read in part, which Tier C reports.
      */
     readonly limit: WalkLimit;
+    /**
+     * True when the layer reached at least one node twice, which is what a YAML
+     * alias does and what nothing else does. Tier C reports it, because a reader
+     * of the file sees one row where the loader sees two.
+     */
+    readonly aliased: boolean;
 }
-/** Nodes one patch layer may be walked through before the walk gives up. */
+/**
+ * The two ceilings that make reading a patch layer terminate.
+ *
+ * They apply to {@link expandAliases}, and through it to everything downstream:
+ * the walk runs over the tree the expansion produced, which holds at most
+ * `MAX_WALK_NODES` nodes nested at most `MAX_WALK_DEPTH` deep, so the walk needs
+ * no ceiling of its own.
+ */
 export declare const MAX_WALK_NODES = 200000;
-/** Nesting one patch layer may reach before the walk gives up. */
+/** Nesting one patch layer may reach before the reader gives up. */
 export declare const MAX_WALK_DEPTH = 200;
 /** Thrown when the patch file cannot be parsed as an entry list. */
 export declare class PatchParseError extends Error {

package/lib/types/inspect.d.ts

@@ -11,8 +11,18 @@
  */
 import { type RegistryProvenance, type Report, type Severity } from './model.ts';
 import { type PluginSource } from './source.ts';
-/** This tool's own version, reported in the JSON document. */
-export declare const TOOL_VERSION = "0.1.0";
+/**
+ * This tool's own version, reported in the JSON document, by `--version`, and
+ * in the recorded ecosystem measurement.
+ *
+ * Read from this package's own `package.json` rather than written down a second
+ * time. A constant is a copy that only a release checklist keeps honest, and it
+ * stopped being honest for two releases: every report claimed `0.1.0` while the
+ * published package was `0.2.1`. The manifest sits one directory above this
+ * module in the source tree, in `lib/` after a build, and in the published
+ * tarball, so the same relative path resolves in all three.
+ */
+export declare const TOOL_VERSION: string;
 /** This tool's package name, reported in the JSON document. */
 export declare const TOOL_NAME = "dsh-plugin-inspector";
 /**

package/lib/types/knowledge.d.ts

@@ -110,6 +110,30 @@ export declare const SKILL_ROOT_CONFIG_KEYS: readonly string[];
  * only needs one of these to run code before the user has read a line of it.
  */
 export declare const INSTALL_LIFECYCLE_SCRIPTS: readonly string[];
+/** One thing a lifecycle command can do that a build never needs to. */
+export interface LifecycleSignal {
+    readonly id: string;
+    readonly pattern: RegExp;
+    /** What the match means, phrased for a report. */
+    readonly meaning: string;
+}
+/**
+ * Command shapes that make an install lifecycle script the attack rather than
+ * the build.
+ *
+ * The case this table is for is the one where the command line itself fetches,
+ * decodes, or evaluates: the whole attack sits in `package.json` and there is
+ * no shipped module to read. A lifecycle hook alone does not distinguish that
+ * from a build, which is why the hook is a category at `medium` and only the
+ * command raises it.
+ *
+ * Each pattern is chosen against the measured false-positive side rather than
+ * against the idea of a build script. The five packages in the pinned corpus
+ * that declare a hook run `tsdown`, `npm run build`, `husky`, and
+ * `node scripts/prepare.mjs`; running a shipped file is what a build hook is, so
+ * that shape is deliberately not a signal here.
+ */
+export declare const LIFECYCLE_SIGNALS: readonly LifecycleSignal[];
 /** Entry fields the loader never interpolates: a `!!js` node here is inert data. */
 export declare const STATIC_ENTRY_FIELDS: readonly string[];
 /**

package/lib/types/source.d.ts

@@ -26,11 +26,20 @@ export declare const MAX_FILE_BYTES: number;
 export declare const MAX_TOTAL_BYTES: number;
 /** Largest number of files the analyzer will consider. */
 export declare const MAX_ENTRIES = 10000;
+/**
+ * Decompressed tar bytes one tarball may produce before the read is abandoned.
+ *
+ * Eight times the in-memory ceiling. A plugin tarball is never this large, and
+ * one that is has already answered the only question worth asking about it.
+ */
+export declare const MAX_STREAM_BYTES: number;
 /** The resource ceilings one read runs under. */
 export interface ReadLimits {
     readonly maxFileBytes: number;
     readonly maxTotalBytes: number;
     readonly maxEntries: number;
+    /** Decompressed tar bytes one tarball may produce before the read is abandoned. */
+    readonly maxStreamBytes: number;
 }
 /** The shipping ceilings. Tests substitute smaller ones to exercise each cap. */
 export declare const DEFAULT_LIMITS: ReadLimits;
@@ -58,13 +67,6 @@ export interface PluginSource {
     /** Working-tree files npm would not publish, and which were therefore not read. */
     readonly unpublishedFiles: number;
 }
-/**
- * Decompressed tar bytes one tarball may produce before the read is abandoned.
- *
- * Eight times the in-memory ceiling. A plugin tarball is never this large, and
- * one that is has already answered the only question worth asking about it.
- */
-export declare const MAX_STREAM_BYTES: number;
 /**
  * Read the package under analysis.
  * @param target - a plugin directory, or a `.tgz` / `.tar.gz` npm tarball.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-inspector",
-  "version": "0.2.1",
+  "version": "0.4.0",
   "description": "Know what a DeepSeek Harness plugin does before you install it — static pre-install analysis of a plugin directory or tarball",
   "license": "MIT",
   "author": "Ivan Tyshchenko",