d-danfe 2.0.0
Visualizador de DANFE em HTML
d-danfe@2.0.0 was published on 2018-08-28. Its manifest declares 2 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 d-danfe versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-08-28T18:50:44.086Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 94.17 KiB |
| Published file count | 7 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 1 |
| Repository forks | 0 |
Install d-danfe 2.0.0
npm install d-danfe@2.0.0 pnpm add d-danfe@2.0.0 yarn add d-danfe@2.0.0
Runtime dependencies
- d-nfe ^1.3.0
- handlebars ^4.0.11
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.
- d-nfe@1.3.0 — direct
- djf-xml@1.0.12 — indirect
- handlebars@4.7.10 — direct
- minimist@1.2.8 — indirect
- neo-async@2.6.2 — indirect
- source-map@0.6.1 — indirect
- uglify-js@3.19.3 — indirect
- wordwrap@1.0.0 — indirect
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 | 0/10 — Found 0/23 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| License | 10/10 — license file detected |
Evidence and freshness
- https://registry.npmjs.org/d-danfe/2.0.0 — retrieved 2026-10-30T06:28:17.816Z
- https://api.deps.dev/v3/systems/npm/packages/d-danfe/versions/2.0.0:dependencies — retrieved 2026-10-30T05:51:10.390Z
- https://api.deps.dev/v3/systems/npm/packages/d-danfe/versions/2.0.0 — retrieved 2026-10-30T05:51:10.362Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fdouglasselias%2Fdjf-danfe — retrieved 2026-10-30T05:51:10.513Z