node-import-ts 1.0.3
node-import-ts@1.0.3 was published on 2019-07-30. Its manifest declares 3 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 node-import-ts versions · Permanent reference to 1.0.3 · Latest release
Package specifications
| Version | 1.0.3 |
|---|---|
| License declaration | ISC |
| Published | 2019-07-30T03:48:50.290Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 4.08 KiB |
| Published file count | 8 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 1 |
| Repository forks | 1 |
Install node-import-ts 1.0.3
npm install node-import-ts@1.0.3 pnpm add node-import-ts@1.0.3 yarn add node-import-ts@1.0.3
Runtime dependencies
- @types/node ^12.6.2
- import-fresh ^3.1.0
- typescript ^3.5.3
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.
- @types/node@12.20.55 — direct
- callsites@3.1.0 — indirect
- import-fresh@3.3.1 — direct
- parent-module@1.0.1 — indirect
- resolve-from@4.0.0 — indirect
- typescript@3.9.10 — 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 | 0/10 — Found 1/14 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 |
| 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 |
| License | 0/10 — license file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/node-import-ts/1.0.3 — retrieved 2026-10-29T17:19:01.995Z
- https://api.deps.dev/v3/projects/github.com%2Fchenshuai2144%2Fnode-require-ts — retrieved 2026-10-29T16:53:02.042Z
- https://api.deps.dev/v3/systems/npm/packages/node-import-ts/versions/1.0.3:dependencies — retrieved 2026-10-29T17:19:02.551Z
- https://api.deps.dev/v3/systems/npm/packages/node-import-ts/versions/1.0.3 — retrieved 2026-10-29T17:19:02.527Z