@firebase/performance-types 0.1.0-canary.1588990b7

@firebase/performance Types

@firebase/performance-types@0.1.0-canary.1588990b7 was published on 2022-02-24. Its manifest declares 0 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 @firebase/performance-types versions · Permanent reference to 0.1.0-canary.1588990b7 · Latest release

Package specifications

Version0.1.0-canary.1588990b7
License declarationApache-2.0
Published2022-02-24T19:00:58.733Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.79 KiB
Published file count3
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars5155
Repository forks1041

Install @firebase/performance-types 0.1.0-canary.1588990b7

npm install @firebase/performance-types@0.1.0-canary.1588990b7
pnpm add @firebase/performance-types@0.1.0-canary.1588990b7
yarn add @firebase/performance-types@0.1.0-canary.1588990b7

Runtime dependencies

  • None declared

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.

Maintained10/10 — 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Code-Review8/10 — Found 24/27 approved changesets -- score normalized to 8
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions7/10 — detected GitHub workflow tokens with excessive permissions
License9/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies10/10 — all dependencies are pinned
Security-Policy10/10 — security policy file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool is not run on all commits -- score normalized to 7

Evidence and freshness