issue-parser 2.3.0
Parser for Github, GitLab, Bitbucket and Waffle issues actions, references and mentions
issue-parser@2.3.0 was published on 2018-09-01. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All issue-parser versions · Permanent reference to 2.3.0 · Latest release
Package specifications
| Version | 2.3.0 |
|---|---|
| License declaration | MIT |
| Published | 2018-09-01T03:24:39.168Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 30.29 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 23 |
| Repository forks | 4 |
Install issue-parser 2.3.0
npm install issue-parser@2.3.0 pnpm add issue-parser@2.3.0 yarn add issue-parser@2.3.0
Runtime dependencies
- lodash.isstring ^4.0.1
- lodash.capitalize ^4.2.1
- lodash.escaperegexp ^4.1.2
- lodash.isplainobject ^4.0.6
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.
- lodash.capitalize@4.2.1 — direct
- lodash.escaperegexp@4.1.2 — direct
- lodash.isplainobject@4.0.6 — direct
- lodash.isstring@4.0.1 — 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.
Evidence and freshness
- https://registry.npmjs.org/issue-parser/2.3.0 — retrieved 2026-10-29T11:52:13.204Z
- https://api.deps.dev/v3/projects/github.com%2Fsemantic-release%2Fissue-parser — retrieved 2026-10-29T10:55:59.098Z
- https://api.deps.dev/v3/systems/npm/packages/issue-parser/versions/2.3.0 — retrieved 2026-10-29T11:52:13.736Z
- https://api.deps.dev/v3/systems/npm/packages/issue-parser/versions/2.3.0:dependencies — retrieved 2026-10-29T11:52:13.772Z