No PHP application runtime
Package inventory and application files are checked for PHP runtime packages and executable PHP files.
Name your coin. Add an image.
Connect your wallet.
Launch on Pump.fun.
No PHP runtime. No application SSH server.
No PHP or SSH service for attackers to target in this app.Other website, wallet and token risks remain.A Pump.fun launcher without PHP or an app SSH server. Tap around to see why.
Coins launched here, confirmed on Solana. Rankings don’t rate a coin’s safety.
One page. Your wallet. A launch on Pump.fun.
No PHP runtime. No application SSH server. Here’s the proof.
These checks cover Pump Hack Protection’s packaged browser code and JavaScript Worker. Hosting-provider internals, external RPCs, wallets, and Pump.fun’s program are outside this inventory.
Loading release inventory…Package inventory and application files are checked for PHP runtime packages and executable PHP files.
The Worker implements HTTP handlers. There is no packaged sshd, operating-system image, or SSH listener in this application.
Your browser fetches this release’s files and compares their SHA-256 hashes with the published manifest.
The browser builds the Pump.fun instruction. The wallet signs; the network confirms. No backend receives wallet private keys.
Build evidence is not an independent audit. A source listing or closed port alone cannot prove the entire hosting environment.
The standalone verifier checks the published file hashes.
Review the source and compare the release fingerprint separately.
Removing PHP and an application SSH service avoids those components’ attack paths in our application. It does not guarantee protection against every exploit, compromised account, malicious signature request, dependency vulnerability, or onchain program flaw. Files and backend declarations are published by Pump Hack Protection; independent production attestation remains pending.