@oslojs/crypto 0.6.1
A very basic crypto library
@oslojs/crypto@0.6.1 was published on 2024-07-24. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
All @oslojs/crypto versions · Permanent reference to 0.6.1 · Latest release
Package specifications
| Version | 0.6.1 |
|---|---|
| License declaration | MIT |
| Published | 2024-07-24T02:06:48.062Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 71.63 KiB |
| Published file count | 49 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @oslojs/crypto 0.6.1
npm install @oslojs/crypto@0.6.1 pnpm add @oslojs/crypto@0.6.1 yarn add @oslojs/crypto@0.6.1
Runtime dependencies
- @oslojs/asn1 0.2.2
- @oslojs/binary 0.4.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @oslojs/asn1@0.2.2 — direct
- @oslojs/binary@0.2.3 — indirect
- @oslojs/binary@0.4.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- https://registry.npmjs.org/%40oslojs%2Fcrypto/0.6.1 — retrieved 2026-10-31T08:12:51.007Z
- https://api.deps.dev/v3/systems/npm/packages/%40oslojs%2Fcrypto/versions/0.6.1 — retrieved 2026-10-31T08:12:51.405Z
- https://api.deps.dev/v3/systems/npm/packages/%40oslojs%2Fcrypto/versions/0.6.1:dependencies — retrieved 2026-10-31T08:12:51.422Z