Update esm-asar-entrypoints

[krombel]

just a merge of main into esm-asar-entrypoints

This intended to update #101.

A more familiar view might be the diff to main.

It is working in this state for me right now for an esm build.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	husky@​8.0.3 ⏵ 9.1.7	+1		-17
	@​tsconfig/​node22@​22.0.1
	vitest@​3.1.3
	@​types/​node@​22.10.10
	@​electron/​get@​3.0.0 ⏵ 4.0.0	+3			+2
	@​electron/​asar@​3.2.7 ⏵ 4.0.0	+1
	typescript@​5.2.2 ⏵ 5.8.3
	lint-staged@​15.0.2 ⏵ 16.1.0	+1		+1	-2
	prettier@​3.0.3 ⏵ 3.5.3	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: ? → npm/vitest@3.1.3 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		High CVE: npm glob CLI: Command injection via -c/--cmd executes matches with shell:true CVE: GHSA-5j98-mcp5-4vw2 glob CLI: Command injection via -c/--cmd executes matches with shell:true (HIGH) Affected versions: >= 11.0.0 < 11.1.0; >= 10.2.0 < 10.5.0 Patched version: 11.1.0 From: ? → npm/@electron/asar@4.0.0 → npm/glob@11.0.2 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@11.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[krombel]

As a comment on socket security => Not actually a security issue.

See https://socket.dev/npm/package/vitest/alerts/3.2.3?tab=dependencies&alert_name=obfuscatedFile
it is only used in tests where it handles base64 encoded data to test the package. Not used outside of tests