protractor 0.0.0

BlockingProxy

protractor@0.0.0 was published on 2016-03-25. 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.

Deprecated: We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular

All protractor versions · Permanent reference to 0.0.0 · Latest release

Package specifications

Version0.0.0
License declarationMIT
Published2016-03-25T05:51:04.645Z
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 sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars8660
Repository forks2243

Install protractor 0.0.0

npm install protractor@0.0.0
pnpm add protractor@0.0.0
yarn add protractor@0.0.0

Runtime dependencies

  • None declared

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.

    Maintained0/10 — project is archived
    Code-Review5/10 — Found 15/29 approved changesets -- score normalized to 5
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Binary-Artifacts10/10 — no binaries found in the repo
    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    License10/10 — license file detected
    Fuzzing0/10 — project is not fuzzed
    Security-Policy10/10 — security policy file detected
    Branch-Protection4/10 — branch protection is not maximal on development and all release branches
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness