@agoric/assert
Advanced tools
An assertion library that keeps sensitive data outside of the Error.
Throw (using provided error message) if expression is false. Assert that expr is truthy, with an optional details to describe the assertion. It is a tagged template literal like
assert(expr, details`....`);
If expr is falsy, then the template contents are reported to the console and also in a thrown error.
The literal portions of the template are assumed non-sensitive, as
are the typeof types of the substitution values. These are
assembled into the thrown error message. The actual contents of the
substitution values are assumed sensitive, to be revealed to the
console only. We assume only the virtual platform's owner can read
what is written to the console, where the owner is in a privileged
position over computation running on that platform.
The optional details can be a string for backwards compatibility
with the nodejs assertion library.
FAQs
Assert expression support that protects sensitive data
The npm package @agoric/assert receives a total of 1,908 weekly downloads. As such, @agoric/assert popularity was classified as popular.
We found that @agoric/assert demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.