Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion .deepsec/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,23 @@
"type": "module",
"workspaces": [],
"packageManager": "pnpm@9.15.4",
"engines": {
"node": ">=22.19.0"
},
"pnpm": {
"overrides": {
"fast-uri": ">=3.1.4 <4",
"hono": ">=4.12.27 <5",
"@hono/node-server": ">=2.0.5 <3",
"undici": ">=7.28.0 <8",
"tar": ">=7.5.21 <8",
"qs": ">=6.15.2 <7",
"body-parser": ">=2.3.0 <3",
"brace-expansion@>=3": ">=5.0.8 <6",
"zod": ">=4.4.0 <5"
}
},
"dependencies": {
"deepsec": "^2.0.8"
"deepsec": "^2.2.9"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Raise the scanner workspace's Node requirement

When .deepsec is installed with Node 22.14 (the version used throughout this repository's workflows), this upgrade pulls @earendil-works/pi-coding-agent@0.81.1 and related packages, all of which declare node >=22.19.0 in the new lockfile. An engine-strict installation therefore fails, while a non-strict installation leaves the documented scanner commands running on an unsupported runtime; declare/document Node >=22.19 for this workspace or retain a compatible Deepsec version.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in c936a21: .deepsec/package.json now declares engines.node: >=22.19.0, so engine-strict installs fail fast on older runtimes instead of leaving the scanner on an unsupported Node.

}
}
Loading