- esy builds are happening in an isolated environment with only specified dependencies available
- esy executes build processes under sandboxing (so builds can't write into arbitrary locations, we have some work to do here though)
- esy has feature which allows to rewrite binaries to remove prefix paths from them.
As for package signing+verification (assuming you are talking about source code) we do only integrity checks now for packages downloaded from npm and via opam.
EDIT: wording