@arikajs/cli MIT 27 versions

@arikajs/cli

npm Repository Homepage

The command-line interface for the ArikaJS framework.

27

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

prakashtank

Keywords

arikajsframeworknode.jstypescriptcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:@arikajs/database	AI (npm-metadata): file: deps are monorepo-internal siblings; stable pattern for this package.	ai	2026/05/31
npm-metadata	url-dep:@arikajs/docs	AI (npm-metadata): file: deps are monorepo-internal siblings; stable pattern for this package.	ai	2026/05/31
npm-metadata	url-dep:@arikajs/console	AI (npm-metadata): file: deps are monorepo-internal siblings; stable pattern for this package.	ai	2026/05/31
phantom-deps	phantom-dep:typescript	AI (phantom-deps): Compiler referenced via tsc script, not directly imported.	ai	2026/05/30
phantom-deps	phantom-dep:@arikajs/docs	AI (phantom-deps): Same-org companion package; expected indirect reference.	ai	2026/05/30
semgrep	semgrep:dynamic-require	AI (semgrep): Framework route-loading pattern using path.join with known paths; stable across versions.	ai	2026/05/30
phantom-deps	phantom-dep:tsx	AI (phantom-deps): Dev tool referenced in config/scripts, not directly imported.	ai	2026/05/30
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @arikajs/cli package; Levenshtein match to 'joi' is coincidental, not a typosquat.	ai	2026/05/29

Versions (showing 27 of 27)

Version	Deps	Published
0.10.19	13 / 4	2026-04-26
0.10.17	12 / 4	2026-04-26
0.10.16	12 / 4	2026-04-26
0.10.15	12 / 4	2026-04-26
0.10.14	12 / 4	2026-04-26
0.10.13	11 / 4	2026-04-26
0.10.12	11 / 4	2026-04-15
0.10.11	11 / 4	2026-04-15
0.10.10	11 / 4	2026-04-14
0.10.9	11 / 4	2026-04-13
0.10.8	11 / 4	2026-04-12
0.10.7	11 / 4	2026-03-24
0.10.6	10 / 4	2026-03-23
0.10.5	10 / 4	2026-03-23
0.10.4	10 / 4	2026-03-22
0.10.3	10 / 4	2026-03-22
0.10.2	10 / 4	2026-03-15
0.10.1	10 / 4	2026-03-15
0.10.0	10 / 4	2026-03-15
0.0.8	9 / 4	2026-03-15
0.0.7	9 / 4	2026-03-15
0.0.6	9 / 4	2026-03-15
0.0.5	9 / 4	2026-03-15
0.0.4	5 / 4	2026-02-21
0.0.3	5 / 4	2026-02-21
0.0.2	5 / 4	2026-02-21
0.0.1	5 / 4	2026-02-21

v0.10.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.