codex-supermemory - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

dist/package.json

+{
+  "type": "commonjs"
+}

dist/skills/supermemory-forget/SKILL.md

+---
+name: supermemory-forget
+description: Remove outdated or incorrect information from memory. Use when user says something is no longer true, wants to delete a memory, or information has changed.
+allowed-tools: Bash(node:*)
+---
+
+# Forget
+
+Remove outdated or incorrect information from Supermemory.
+
+## When to Use
+
+- User says something is no longer true or has changed
+- User explicitly asks to forget or delete a memory
+- Information has become outdated or incorrect
+
+## How to Forget
+
+Describe the content to forget — the system will find and remove matching memories:
+
+```bash
+node ~/.codex/supermemory/forget-memory.js "DESCRIPTION_OF_WHAT_TO_FORGET"
+```
+
+## Examples
+
+- User says "I no longer use React, I switched to Vue":
+
+  ```bash
+  node ~/.codex/supermemory/forget-memory.js "user prefers React for frontend development"
+  ```
+
+- User says "forget that API endpoint, it changed":
+
+  ```bash
+  node ~/.codex/supermemory/forget-memory.js "API endpoint for user authentication"
+  ```
+
+## After Forgetting
+
+Confirm to the user that the memory has been removed. If they mentioned new information to replace it, use the supermemory-save skill to save the updated information.

dist/skills/supermemory-save/SKILL.md

+---
+name: supermemory-save
+description: Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for future reference.
+allowed-tools: Bash(node:*)
+---
+
+# Super Save
+
+Save important project knowledge based on what the user wants to preserve.
+
+## Step 1: Understand User Request
+
+Analyze what the user is asking to save from the conversation.
+
+## Step 2: Format Content
+
+Format the content to capture the key context:
+
+```
+[SAVE:<date>]
+
+<User> wanted to <goal/problem>.
+
+The approach taken was <approach/solution>.
+
+Decision: <decision made>.
+
+<key details, files if relevant>
+
+[/SAVE]
+```
+
+Example:
+```
+[SAVE:2025-06-15]
+
+User wanted to create a skill for saving project knowledge.
+
+The approach taken was using a separate container tag for shared team knowledge.
+
+Decision: Keep it simple - no transcript fetching, just save what user asks for.
+
+Files: src/save-memory.ts, src/skills/super-save/SKILL.md
+
+[/SAVE]
+```
+
+Keep it natural. Capture the conversation flow.
+
+## Step 3: Save
+
+```bash
+node ~/.codex/supermemory/save-memory.js "FORMATTED_CONTENT"
+```

dist/skills/supermemory-search/SKILL.md

+---
+name: supermemory-search
+description: Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.
+allowed-tools: Bash(node:*)
+---
+
+# Super Search
+
+Search Supermemory for past coding sessions, decisions, and saved information.
+
+## How to Search
+
+Run the search script with the user's query and optional scope flag:
+
+```bash
+node ~/.codex/supermemory/search-memory.js [--user|--project|--both] "USER_QUERY_HERE"
+```
+
+### Scope Flags
+
+- `--both` (default): Search both personal and project memories in parallel
+- `--user`: Search personal/user memories across sessions
+- `--project`: Search project-specific memories
+
+### Options
+
+- `--no-profile`: Skip fetching the user profile summary (included by default)
+
+## Examples
+
+- User asks "what did I work on yesterday":
+
+  ```bash
+  node ~/.codex/supermemory/search-memory.js "work yesterday recent activity"
+  ```
+
+- User asks "how did we implement auth" (project-specific):
+
+  ```bash
+  node ~/.codex/supermemory/search-memory.js --project "authentication implementation"
+  ```
+
+- User asks "what are my coding preferences":
+  ```bash
+  node ~/.codex/supermemory/search-memory.js --user "coding preferences style"
+  ```
+
+## Present Results
+
+The script outputs formatted memory results with relevance information. Present them clearly to the user and offer to search again with different terms if needed.

package.json

 {
   "name": "codex-supermemory",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Persistent memory for OpenAI Codex CLI — powered by Supermemory",
@@ -5,0 +5,0 @@ "type": "module",

New alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Network access

Supply chain risk

This module accesses the network.

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 5 instances

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Improved metrics

Total package byte prevSize

434991

6750.25%

Number of package files

12

500%

Lines of code

12044

Infinity%

Worsened metrics

Number of low supply chain risk alerts

44

Infinity%

Number of medium supply chain risk alerts

47

4600%

No dependency changes