Skip to content

Separating Core and CLI #36

Closed
Closed
@caffeine-addictt

Description

@caffeine-addictt

Question

Describe your question or ask for support

Should core and CLI be separated into 2 packages, with CLI requiring core as a dependency?

Reasons

The CLI is undoubtedly not as utilized and adds bloat to core library for.
This will add more libraries that developers have to watch for version releases and CVEs.

Furthermore, the CLI is not stable as due to my limited knowledge, I've had to rely on eval() which is an attack vector for arbitrary code execution. By continuing to include this as a primary dependency to thread may introduce unintended security vulnerabilities from a not-as-utilized feature.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions