@tryinget/pi-session-compaction@0.4.0
Dedicated Pi package for custom session compaction summaries.
AI Security Review
scanned 17h ago · by lpm-firewall-aiThe package performs runtime metadata telemetry during compaction and recall, with no opt-out found in the reviewed source. The observed payloads are limited to operational metrics, so this warrants a warning rather than a block.
Static reason
No blocking static signals were detected.
Trigger
Compaction runs, or the user invokes session recall.
Impact
Telemetry is not shown to include prompts or file contents, but users have no visible package setting to disable its collection.
Mechanism
The package calls telemetry emitters with quality and recall metadata. The dependency source was unresolved, so the destination and transport could not be confirmed.
AI rationale
The package performs runtime metadata telemetry during compaction and recall, with no opt-out found in the reviewed source. The observed payloads are limited to operational metrics, so this warrants a warning rather than a block.
Evidence
extensions/session-compaction/quality-telemetry.jsextensions/session-compaction/guarded-handler.jsextensions/session-compaction/session-recall.jsdocs/p1-continuity.md
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The extension dynamically imports @tryinget/pi-telemetry/emit for telemetry.
- Compaction automatically emits quality metrics, including summary length, message counts, budget values, and timing.
- The recall feature emits usage metrics when a recall command or tool is used.
- Package documentation describes metadata-only quality telemetry, but the reviewed source shows no opt-out mechanism.
Evidence against
- Telemetry payloads shown contain counts, modes, and status values rather than prompt or file contents.
- Telemetry calls are wrapped as best-effort and do not block compaction or recall.
- No fixed network endpoint or install-time lifecycle script was identified.
Behavioral surface
CryptoFilesystem
HighEntropyStrings
NoLicense
Source & flagged code
6 flaggedextensions/session-compaction/managed-block-codec.jsView file
•stage = ast_semantic_analysis; reason = ast_alias_growth_limit_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
extensions/session-compaction/managed-block-codec.jsView on unpkgpackage.jsonView file
•dependencies changed=@tryinget/pi-model-selection,@tryinget/pi-telemetry
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgextensions/session-compaction/quality-telemetry.jsView file
Findings
1 Critical1 High4 Medium4 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limitedextensions/session-compaction/managed-block-codec.js
MediumAi Review Evidenceextensions/session-compaction/quality-telemetry.js
MediumAi Review Evidenceextensions/session-compaction/guarded-handler.js
MediumAi Review Evidenceextensions/session-compaction/session-recall.js
MediumAi Review Evidencedocs/p1-continuity.md
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowNo License
Affected versions and remediation
This report applies to @tryinget/pi-session-compaction@0.4.0.
See all versions of @tryinget/pi-session-compaction for other recorded verdicts.
- Review the evidence and your use of @tryinget/pi-session-compaction@0.4.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.