@agoric/internal
Advanced tools
Externally unsupported utilities internal to agoric-sdk
NOTE: unsupported
This package contains code that is required by agoric-sdk and not meant to be imported anywhere else.
Like all @agoric packages it follows Semantic Versioning. Unlike the others, it will never have a stable API. In terms of SemVer spec item 4, it will never reach 1.0:
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
It is meant to be a home for modules that have no Agoric-specific dependencies themselves. It does depend on a these other @agoric packages but they are all destined to migrate out of the repo,
This package may not take dependencies on any others in this repository.
It must never export ambient types.
It should not be imported by deep imports. Eventually this will be enforced by exports but the tooling isn't ready:
- https://github.com/import-js/eslint-plugin-import/issues/1810
- https://github.com/microsoft/TypeScript/issues/33079 (or some related problem with JSdoc types)
FAQs
Externally unsupported utilities internal to agoric-sdk
The npm package @agoric/internal receives a total of 8,454 weekly downloads. As such, @agoric/internal popularity was classified as popular.
We found that @agoric/internal demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
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.
