analytics-utils 0.1.3

Analytics utility functions used by 'analytics' module

analytics-utils@0.1.3 was published on 2020-04-16. 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 analytics-utils versions · Permanent reference to 0.1.3 · Latest release

Package specifications

Version0.1.3
License declarationMIT
Published2020-04-16T05:25:16.899Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size88.35 KiB
Published file count9
Package typeNot declared
ES module entrylib/analytics-utils.es.js
Default entrylib/analytics-utils.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars2669
Repository forks266

Install analytics-utils 0.1.3

npm install analytics-utils@0.1.3
pnpm add analytics-utils@0.1.3
yarn add analytics-utils@0.1.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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-Review0/10 — Found 2/28 approved changesets -- score normalized to 0
Maintained10/10 — 13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy9/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness