@microsoft/dynamicproto-js
Microsoft Dynamic Proto Utility
@microsoft/dynamicproto-js@2.0.5 was published on 2026-05-28. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @microsoft/dynamicproto-js versions · Permanent reference to 2.0.5
Package specifications
| Version | 2.0.5 |
|---|---|
| License declaration | MIT |
| Published | 2026-05-28T00:51:39.320Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 3264.62 KiB |
| Published file count | 38 |
| Package type | Not declared |
| ES module entry | ./dist-es5/DynamicProto.js |
| Default entry | ./dist/es5/node/dynamicproto-js.js |
| Side effects declaration | false |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 29 |
| Repository forks | 16 |
Install @microsoft/dynamicproto-js 2.0.5
npm install @microsoft/dynamicproto-js@2.0.5 pnpm add @microsoft/dynamicproto-js@2.0.5 yarn add @microsoft/dynamicproto-js@2.0.5
Runtime dependencies
- @nevware21/ts-utils >= 0.14.0 < 2.x
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.
- @nevware21/ts-utils@0.16.0 — direct
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-Review | 10/10 — all changesets reviewed |
|---|---|
| Maintained | 3/10 — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Security-Policy | 10/10 — security policy file detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 8/10 — dependency not pinned by hash detected -- score normalized to 8 |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 8/10 — branch protection is not maximal on development and all release branches |
| SAST | 7/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/%40microsoft%2Fdynamicproto-js/2.0.5 — retrieved 2026-10-29T13:15:00.922Z
- https://api.deps.dev/v3/systems/npm/packages/%40microsoft%2Fdynamicproto-js/versions/2.0.5 — retrieved 2026-10-29T13:15:01.612Z
- https://api.deps.dev/v3/systems/npm/packages/%40microsoft%2Fdynamicproto-js/versions/2.0.5:dependencies — retrieved 2026-10-29T13:15:01.670Z
- https://api.deps.dev/v3/projects/github.com%2Fmicrosoft%2FDynamicProto-JS — retrieved 2026-10-29T13:15:01.791Z