Does npm provenance mean a package is safe?
No. npm explicitly says established provenance does not guarantee the absence of malicious code. It provides a verifiable connection to source and build information, which still needs review for the decision you are making.
The npm provenance guide explains that scope. A familiar maintainer handle is a different observation from an attestation about a particular artifact. Use the npm profile guide for the public publishing-account reference; ProfileTrace does not verify attestations or analyze dependency behavior.
For your project reviewer, keep the package, version and provenance reference together. That makes the claimed source/build connection available to examine without treating an account resemblance as authentication.
A valid connection can still lead to code that needs scrutiny. Provenance adds information to artifact review; it does not answer the entire safety question. Don’t install a disputed version merely to see whether a publishing account is genuine.
Results are leads, not proof of identity. ProfileTrace is not a background check and cannot be used for hiring, housing, credit or insurance decisions under the Fair Credit Reporting Act (FCRA).