joseph/internal-joseph
1
0
Fork 0
Code Issues 21 Pull requests Projects Releases Packages Wiki Activity Actions

[OneDev #16] feat(security): dependency/install source guardian — scan packages and install scripts for supply chain issues #29

New issue
Open
opened 2026-05-24 04:46:40 +00:00 by joseph · 0 comments
joseph commented 2026-05-24 04:46:40 +00:00
Owner
Copy link

Imported from OneDev issue #16 (id 35293)
Original project: internal-joseph
Original state: Open
Original submitterId: 5
Original submitDate: 2026-04-11T15:11:19.606+00:00
Original lastActivity: {'date': '2026-04-11T15:11:19.606+00:00', 'description': 'opened', 'userId': 5}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

A recurring scan layer across PCT repos and install surfaces that checks: (1) dependencies (npm, Go modules, cargo, pip) for known CVEs and suspicious version bumps, (2) install scripts (irm pctbin.com/* | iex, agent.ps1, etc.) for source integrity, (3) upstream package sources for hijack indicators (maintainer change, sudden new owner, massive diff on patch version). Could run as a scheduled agent or CI hook on OneDev.

Why

PCT now ships install scripts consumed directly by client endpoints (sshubble agent, station, sos.ps1). A compromised upstream package or a tampered install script is a supply chain attack vector into client machines. No current scanning exists across PCT's 35+ repos. The irm ... | iex pattern especially needs integrity verification.

Open questions

  • Scope: PCT-authored repos only, or also third-party deps pulled in by those repos?
  • Tooling: OSV-scanner, Trivy, Socket.dev, or a lightweight custom check?
  • Output surface: OneDev issues filed on findings, or a dashboard panel on saas.pctbin.com?
  • Install script integrity: checksum pinning, subresource integrity headers, or signed releases?
Imported from OneDev issue #16 (id 35293) Original project: internal-joseph Original state: Open Original submitterId: 5 Original submitDate: 2026-04-11T15:11:19.606+00:00 Original lastActivity: {'date': '2026-04-11T15:11:19.606+00:00', 'description': 'opened', 'userId': 5} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea A recurring scan layer across PCT repos and install surfaces that checks: (1) dependencies (npm, Go modules, cargo, pip) for known CVEs and suspicious version bumps, (2) install scripts (`irm pctbin.com/* | iex`, agent.ps1, etc.) for source integrity, (3) upstream package sources for hijack indicators (maintainer change, sudden new owner, massive diff on patch version). Could run as a scheduled agent or CI hook on OneDev. ## Why PCT now ships install scripts consumed directly by client endpoints (sshubble agent, station, sos.ps1). A compromised upstream package or a tampered install script is a supply chain attack vector into client machines. No current scanning exists across PCT's 35+ repos. The `irm ... | iex` pattern especially needs integrity verification. ## Open questions - Scope: PCT-authored repos only, or also third-party deps pulled in by those repos? - Tooling: OSV-scanner, Trivy, Socket.dev, or a lightweight custom check? - Output surface: OneDev issues filed on findings, or a dashboard panel on saas.pctbin.com? - Install script integrity: checksum pinning, subresource integrity headers, or signed releases?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
joseph/internal-joseph#29
No description provided.