proxy-compare 3.0.1

Compare two objects using accessed properties with Proxy

proxy-compare@3.0.1 was published on 2024-11-22. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All proxy-compare versions · Permanent reference to 3.0.1 · Latest release

Package specifications

Version3.0.1
License declarationMIT
Published2024-11-22T00:41:03.049Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified size2.55 KiB
Minified + gzip1.20 KiB
Unpacked distribution size65.28 KiB
Published file count9
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies0
Repository stars311
Repository forks19

Install proxy-compare 3.0.1

npm install proxy-compare@3.0.1
pnpm add proxy-compare@3.0.1
yarn add proxy-compare@3.0.1

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.

    Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Code-Review0/10 — Found 2/29 approved changesets -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness