lasso-modules-client 2.0.6
The client-side CommonJS runtime for Lasso.js
lasso-modules-client@2.0.6 was published on 2020-09-17. 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.
All lasso-modules-client versions · Permanent reference to 2.0.6 · Latest release
Package specifications
| Version | 2.0.6 |
|---|---|
| License declaration | Apache-2.0 |
| Published | 2020-09-17T18:37:00.525Z |
| 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 | 77.75 KiB |
| Published file count | 45 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 0 |
| Repository forks | 1 |
Install lasso-modules-client 2.0.6
npm install lasso-modules-client@2.0.6 pnpm add lasso-modules-client@2.0.6 yarn add lasso-modules-client@2.0.6
Runtime dependencies
- raptor-polyfill ^1.0.2
- lasso-package-root ^1.0.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.
- lasso-caching-fs@1.0.2 — indirect
- lasso-package-root@1.0.1 — direct
- raptor-async@1.1.3 — indirect
- raptor-polyfill@1.1.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.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/26 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/lasso-modules-client/2.0.6 — retrieved 2026-10-29T22:01:33.540Z
- https://api.deps.dev/v3/projects/github.com%2Flasso-js%2Flasso-modules-client — retrieved 2026-10-29T19:34:52.502Z
- https://api.deps.dev/v3/systems/npm/packages/lasso-modules-client/versions/2.0.6 — retrieved 2026-10-29T22:01:34.032Z
- https://api.deps.dev/v3/systems/npm/packages/lasso-modules-client/versions/2.0.6:dependencies — retrieved 2026-10-29T22:01:34.052Z