@sentry/cli 1.46.0

A command line utility to work with Sentry. https://docs.sentry.io/hosted/learn/cli/

@sentry/cli@1.46.0 was published on 2019-06-27. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 4.5.0.

All @sentry/cli versions · Permanent reference to 1.46.0 · Latest release

Package specifications

Version1.46.0
License declarationBSD-3-Clause
Published2019-06-27T22:38:22.396Z
Node.js requirement>= 4.5.0
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size46.35 KiB
Published file count12
Package typeNot declared
ES module entryNot declared
Default entryjs/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies15
Repository stars1043
Repository forks255

Install @sentry/cli 1.46.0

npm install @sentry/cli@1.46.0
pnpm add @sentry/cli@1.46.0
yarn add @sentry/cli@1.46.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.

OpenSSF repository checks

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

Code-Review5/10 — Found 10/19 approved changesets -- score normalized to 5
Maintained10/10 — 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts2/10 — binaries present in source code
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
Security-Policy10/10 — security policy file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Packaging10/10 — packaging workflow detected
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
SAST10/10 — SAST tool is run on all commits

Evidence and freshness