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 Declare the new DeepSec Node requirement

On Node 18 or Node 20—the versions still accepted by the declared pnpm 9 toolchain—the documented .deepsec install can complete with engine warnings and then leave the scanner unusable: DeepSec 2.2.9 now installs the @earendil-works/pi-* 0.81.1 packages, all of which require Node >=22.19.0, while this workspace declares no Node engine or setup version. Add an engines.node constraint/documented setup version or retain a DeepSec version compatible with the previously usable runtimes so users fail before attempting scans.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in c4d9c4f: .deepsec/package.json now declares engines.node: >=22.19.0, matching what the @earendil-works/pi-* 0.81.1 packages require, so installs on Node 18/20 fail before anyone attempts a scan.

}
}
Loading