npmpackage.info

Gathering detailed insights and metrics for @endo/zip

@endo/zip

Endo is a distributed secure JavaScript sandbox, based on SES

1.0.9

833

Apache-2.0

JavaScript

3.59 kB

459,821 6.2

Installations

npm install @endo/zip

Score

91.4

Supply Chain

87.3

Quality

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

179

Total

1,689

Closed

217

Merged

1,293

Issues

Open

270

Total

923

Closed

653

Releases

2024-11-13

ses@1.10.0

Published on 13 Nov 2024

View all 1 releases

Developer

endojs

Developer Guide

BETA

Module System

ESM

Min. Node Version

Typescript Support

No

Node Version

18.19.0

NPM Version

lerna/8.1.8/node@v18.19.0+x64 (darwin)

Statistics

833 Stars

6,094 Commits

72 Forks

27 Watching

389 Branches

48 Contributors

Updated on 27 Nov 2024

Bundle Size

11.56 kB

Minified

3.59 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (99.87%)

TypeScript (0.1%)

Shell (0.03%)

Total Downloads

Cumulative downloads

Total Downloads

459,821

Last day

-42.2%

1,602

Compared to previous day

Last week

-45.1%

7,851

Compared to previous week

Last month

87.2%

40,032

Compared to previous month

Last year

78.6%

215,256

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

ava babel-eslint c8 eslint eslint-config-airbnb-base eslint-config-prettier eslint-plugin-eslint-comments eslint-plugin-import prettier typescript

Versions

Endo

Endo is a framework for powerful JavaScript plugin systems and supply chain attack resistance. Endo includes tools for confinement, communication, and concurrency. These include a shim for Hardened JavaScript, an ECMA TC-39 standards track proposal to make JavaScript a safer and more suitable platform for plugin systems.

Agoric and MetaMask rely on Hardened JavaScript and the SES shim as part of systems that sandbox third-party plugins or smart contracts and mitigate supply chain attacks for production web applications, web extensions, and build systems.

Endo protects program integrity both in-process and in distributed systems. Hardened JavaScript protects local integrity, defending an application against supply chain attacks: hacks that enter through upgrades to third-party dependencies. Endo does this by encouraging the Principle of Least Authority.

Since most JavaScript libraries receive powerful capabilities from global objects like fetch or modules like net, LavaMoat generates reviewable policies that determine what capabilities will be distributed to third party dependencies according to evident need, and enforces those policies at runtime with Endo.

For distributed systems, Endo stretches object oriented programming over networks using asynchronous message passing to remote objects with the Handled Promise API and a Capability Transfer Protocol.

Between remote objects and Hardened JavaScript compartments, Endo makes distributed programs easy to program, and easy to reason about integrity. CapTP frees the programmer from needing to create bespoke communication protocols over message ports or byte streams.

Endo combines these components to demonstrate their use for a confined plugin system in the Endo Pet-name Dæmon and its CLI.

Please join the conversation on our Mailing List and Matrix. Reach out if you would like an ivitation to our meetings:

We record a weekly Endo Sync video call .
We recorded a weekly SES video call with the Hardened JavaScript engineering community.
We now meet weekly with ECMA TC-39 ECMAScript Technical Committee TG-3 Security Working Group.

Ruminations on the Name

In Greek, "endo-" means "internal" or "within". This is fitting because Endo runs Node within a safe sandbox. This is fitting in turn because Endo is built on the legacy of Google Caja. In Spanish, "caja" means "box" and is related to the Latin word "capsum" and English "capsule", as in "encapsulate".
Endo is an anagram of Node and Deno. That is to say, we are not Done yet.
The endo command, like the sudo command, is a "do" command. However, instead of escalating privilege, it attenuates privilege.
Endo lets applications endow packages with limited powerful objects and modules. As they say, you can't spell "endow" without "endo"!
So, "E.N.Do" forms the acronym "Encapsulated Node Do".

So, just as "soo-doo" (super user do) and "soo-doh" (like "pseudo") are valid pronunciations of sudo, "en-doh" and "en-doo" are both valid pronunciations of endo.

Principle of Least Authority

The Principle of Least Authority (Wikipedia) states that a software component should only have access to data and resources that enable it to do its legitimate work.

PoLA explained in 3 minutes: Opening Statement on SOSP 50th Anniversary Panel, Mark Miller:

PoLA explained in 15 minutes: Navigating the Attack Surface to achieve a multiplicative reduction in risk, Mark Miller:

Bug Disclosure

Please help us practice coordinated security bug disclosure, by using the instructions in our security guide to report security-sensitive bugs privately.

For non-security bugs, please use the regular Issues page.

License

Endo and its components are Apache 2.0 licensed.

No vulnerabilities found.

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Fuzzing

Determines if the project uses fuzzing.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-test.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/browser-test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-test.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/browser-test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-test.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/browser-test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:230: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:236: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:276: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:285: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:304: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:330: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:121: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:127: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:158: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:164: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:194: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:200: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/depcheck.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/depcheck.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/depcheck.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/depcheck.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/typedoc-gh-pages.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/typedoc-gh-pages.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/typedoc-gh-pages.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/typedoc-gh-pages.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/typedoc-gh-pages.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/typedoc-gh-pages.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/typedoc-gh-pages.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/endojs/endo/typedoc-gh-pages.yml/master?enable=pin
Info: 0 out of 25 GitHub-owned GitHubAction dependencies pinned
Info: 1 out of 1 npmCommand dependencies pinned

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

6.2

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More