Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Deno Dig to tools section #397

Merged
merged 1 commit into from
Oct 29, 2024
Merged

Add Deno Dig to tools section #397

merged 1 commit into from
Oct 29, 2024

Conversation

theGEBIRGE
Copy link
Contributor

Add entry for Deno Dig tool, which is able to extract application code and npm packages from executables produced by deno compile.

Add entry for Deno Dig, which is able to extract application code and npm packages from executables produced by `deno compile`.
Copy link
Member

@kt3k kt3k left a comment

Choose a reason for hiding this comment

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

When does one need to extract application code from compiled binary?

Anyway this looks an interesting an idea. LGTM

@kt3k kt3k merged commit 4676041 into denolib:main Oct 29, 2024
1 check failed
@theGEBIRGE
Copy link
Contributor Author

I made it with security research in mind, maybe a pentesting context: You stumble over a Deno binary and want to know what permissions it has, audit the code for vulnerabilities or get access to code from a private repository.

Probably a niche use case, but learning about how Deno compile works was a lot of fun. :)

Thanks for merging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants