loggly
A client implementation for Loggly cloud Logging-as-a-Service API
loggly@1.1.1 was published on 2016-09-29. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.0.
All loggly versions · Permanent reference to 1.1.1
Package specifications
| Version | 1.1.1 |
|---|---|
| License declaration | MIT |
| Published | 2016-09-29T16:32:25.584Z |
| Node.js requirement | >= 0.8.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/loggly |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 75 |
| Repository stars | 233 |
| Repository forks | 83 |
Install loggly 1.1.1
npm install loggly@1.1.1 pnpm add loggly@1.1.1 yarn add loggly@1.1.1
Runtime dependencies
- request 2.75.x
- timespan 2.3.x
- json-stringify-safe 5.0.x
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.
- json-stringify-safe@5.0.1 — direct
- request@2.75.0 — direct
- timespan@2.3.0 — direct
- aws-sign2@0.6.0 — indirect
- aws4@1.13.2 — indirect
- bl@1.1.2 — indirect
- caseless@0.11.0 — indirect
- combined-stream@1.0.8 — indirect
- extend@3.0.2 — indirect
- forever-agent@0.6.1 — indirect
- form-data@2.0.0 — indirect
- har-validator@2.0.6 — indirect
- hawk@3.1.3 — indirect
- http-signature@1.1.1 — indirect
- is-typedarray@1.0.0 — indirect
- isstream@0.1.2 — indirect
- mime-types@2.1.35 — indirect
- node-uuid@1.4.8 — indirect
- oauth-sign@0.8.2 — indirect
- qs@6.2.6 — indirect
- stringstream@0.0.6 — indirect
- tough-cookie@2.3.4 — indirect
- tunnel-agent@0.4.3 — indirect
- readable-stream@2.0.6 — indirect
- delayed-stream@1.0.0 — indirect
- asynckit@0.4.0 — indirect
- chalk@1.1.3 — indirect
- commander@2.20.3 — indirect
- is-my-json-valid@2.20.6 — indirect
- pinkie-promise@2.0.1 — indirect
- boom@2.10.1 — indirect
- cryptiles@2.0.5 — indirect
- hoek@2.16.3 — indirect
- sntp@1.0.9 — indirect
- assert-plus@0.2.0 — indirect
- jsprim@1.4.2 — indirect
- sshpk@1.18.0 — indirect
- mime-db@1.52.0 — indirect
- punycode@1.4.1 — indirect
- core-util-is@1.0.3 — indirect
- inherits@2.0.4 — indirect
- isarray@1.0.0 — indirect
- process-nextick-args@1.0.7 — indirect
- string_decoder@0.10.31 — indirect
- util-deprecate@1.0.2 — indirect
- ansi-styles@2.2.1 — indirect
- escape-string-regexp@1.0.5 — indirect
- has-ansi@2.0.0 — indirect
- strip-ansi@3.0.1 — indirect
- supports-color@2.0.0 — indirect
- generate-function@2.3.1 — indirect
- generate-object-property@1.2.0 — indirect
- is-my-ip-valid@1.0.1 — indirect
- jsonpointer@5.0.1 — indirect
- xtend@4.0.2 — indirect
- pinkie@2.0.4 — indirect
- assert-plus@1.0.0 — indirect
- extsprintf@1.3.0 — indirect
- json-schema@0.4.0 — indirect
- verror@1.10.0 — indirect
- asn1@0.2.6 — indirect
- assert-plus@1.0.0 — indirect
- bcrypt-pbkdf@1.0.2 — indirect
- dashdash@1.14.1 — indirect
- ecc-jsbn@0.1.2 — indirect
- getpass@0.1.7 — indirect
- jsbn@0.1.1 — indirect
- safer-buffer@2.1.2 — indirect
- tweetnacl@0.14.5 — indirect
- ansi-regex@2.1.1 — indirect
- is-property@1.0.2 — indirect
- assert-plus@1.0.0 — indirect
- core-util-is@1.0.2 — indirect
- assert-plus@1.0.0 — indirect
- assert-plus@1.0.0 — indirect
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-Review | 1/10 — Found 5/27 approved changesets -- score normalized to 1 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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 | 9/10 — license file 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/loggly/1.1.1 — retrieved 2026-10-30T20:17:09.894Z
- https://api.deps.dev/v3/systems/npm/packages/loggly/versions/1.1.1:dependencies — retrieved 2026-10-30T20:17:10.243Z
- https://api.deps.dev/v3/systems/npm/packages/loggly/versions/1.1.1 — retrieved 2026-10-30T20:17:10.243Z
- https://api.deps.dev/v3/projects/github.com%2Fwinstonjs%2Fnode-loggly — retrieved 2026-10-30T20:17:10.709Z