ses 0.12.0

Secure ECMAScript

ses@0.12.0 was published on 2021-02-03. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All ses versions · Permanent reference to 0.12.0 · Latest release

Package specifications

Version0.12.0
License declarationApache-2.0
Published2021-02-03T00:40:23.025Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11932.19 KiB
Published file count59
Package typemodule
ES module entry./ses.js
Default entry./dist/ses.cjs
Side effects declarationNot declared
Direct advisories2
Resolved graph dependencies3
Repository stars1071
Repository forks91

Install ses 0.12.0

npm install ses@0.12.0
pnpm add ses@0.12.0
yarn add ses@0.12.0

Runtime dependencies

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.

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Binary-Artifacts9/10 — binaries present in source code
Fuzzing10/10 — project is fuzzed

Evidence and freshness