@material/circular-progress 15.0.0-canary.95ef196bc.0

The Material Components for the web circular progress component

@material/circular-progress@15.0.0-canary.95ef196bc.0 was published on 2022-10-14. Its manifest declares 8 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 @material/circular-progress versions · Permanent reference to 15.0.0-canary.95ef196bc.0 · Latest release

Package specifications

Version15.0.0-canary.95ef196bc.0
License declarationMIT
Published2022-10-14T23:13:38.434Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count8
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size234.87 KiB
Published file count38
Package typeNot declared
ES module entry./index.js
Default entrydist/mdc.circularProgress.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies8
Repository stars17035
Repository forks2123

Install @material/circular-progress 15.0.0-canary.95ef196bc.0

npm install @material/circular-progress@15.0.0-canary.95ef196bc.0
pnpm add @material/circular-progress@15.0.0-canary.95ef196bc.0
yarn add @material/circular-progress@15.0.0-canary.95ef196bc.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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — project is archived
Code-Review3/10 — Found 10/30 approved changesets -- score normalized to 3
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness