tsickle 0.1.1
Transpile TypeScript code to JavaScript with Closure annotations.
tsickle@0.1.1 was published on 2016-05-02. Its manifest declares 3 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All tsickle versions · Permanent reference to 0.1.1 · Latest release
Package specifications
| Version | 0.1.1 |
|---|---|
| License declaration | MIT |
| Published | 2016-05-02T02:05:15.852Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | build/src/tsickle.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 898 |
| Repository forks | 104 |
Install tsickle 0.1.1
npm install tsickle@0.1.1 pnpm add tsickle@0.1.1 yarn add tsickle@0.1.1
Runtime dependencies
- minimist ^1.2.0
- source-map ^0.4.2
- source-map-support ^0.3.1
Peer requirements
- typescript ^1.8.0 || ^1.9.0-dev
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- amdefine@1.0.1 — indirect
- minimist@1.2.8 — direct
- source-map@0.1.32 — indirect
- source-map@0.4.4 — direct
- source-map-support@0.3.3 — 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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Maintained | 0/10 — project is archived |
| Code-Review | 9/10 — Found 27/30 approved changesets -- score normalized to 9 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 3/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/tsickle/0.1.1 — retrieved 2026-10-29T16:27:54.472Z
- https://api.deps.dev/v3/projects/github.com%2Fangular%2Ftsickle — retrieved 2026-10-29T15:56:44.483Z
- https://api.deps.dev/v3/systems/npm/packages/tsickle/versions/0.1.1 — retrieved 2026-10-29T16:27:54.996Z
- https://api.deps.dev/v3/systems/npm/packages/tsickle/versions/0.1.1:dependencies — retrieved 2026-10-29T16:27:55.014Z