@arbidocs/cli MIT 48 versions

@arbidocs/cli

npm Repository Homepage

CLI tool for interacting with ARBI — login, manage workspaces, upload documents, query the RAG assistant

48

Versions

MIT

License

Yes

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

arbi-dev

Keywords

arbicliragdocument-managemente2e-encryption

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	rapid-publish	AI (publish-pattern): High-frequency monorepo releases; all sibling packages version-lock together, rapid publishes are expected.	ai	2026/05/30
install-scripts	install-script:postinstall	AI (install-scripts): CLI tool with stable postinstall script across versions; no malicious payload detected.	ai	2026/05/22
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped CLI package @arbidocs/cli; no resemblance to joi validation library. Levenshtein match is spurious.	ai	2026/05/17
phantom-deps	phantom-dep:@arbidocs/tui	AI (phantom-deps): Same org scope; likely used transitively or conditionally within the CLI — stable false positive for this package.	ai	2026/05/17

Versions (showing 48 of 48)

Version	Deps	Published
0.3.76	6 / 4	2026-05-29
0.3.75	6 / 4	2026-05-29
0.3.68	6 / 4	2026-05-25
0.3.65	6 / 4	2026-05-22
0.3.64	6 / 4	2026-05-22
0.3.63	6 / 4	2026-05-21
0.3.62	6 / 4	2026-05-21
0.3.61	6 / 4	2026-05-21
0.3.60	6 / 4	2026-05-21
0.3.59	6 / 4	2026-05-16
0.3.57	6 / 4	2026-05-07
0.3.55	6 / 4	2026-05-06
0.3.54	6 / 4	2026-04-30
0.3.53	6 / 4	2026-04-29
0.3.52	6 / 4	2026-04-28
0.3.50	6 / 4	2026-04-23
0.3.49	6 / 4	2026-04-21
0.3.46	6 / 4	2026-04-19
0.3.45	6 / 4	2026-04-17
0.3.44	6 / 4	2026-04-17
0.3.41	6 / 4	2026-04-17
0.3.40	6 / 4	2026-04-17
0.3.39	6 / 4	2026-04-17
0.3.38	6 / 4	2026-04-17
0.3.37	6 / 4	2026-04-17
0.3.35	6 / 4	2026-04-16
0.3.33	6 / 4	2026-04-13
0.3.29	6 / 4	2026-04-11
0.3.28	6 / 4	2026-03-23
0.3.27	6 / 4	2026-03-21
0.3.26	6 / 4	2026-03-19
0.3.24	6 / 4	2026-03-18
0.3.23	6 / 4	2026-03-18
0.3.20	6 / 4	2026-03-12
0.3.18	6 / 4	2026-03-02
0.3.16	6 / 4	2026-02-27
0.3.15	6 / 4	2026-02-27
0.3.14	6 / 4	2026-02-27
0.3.13	6 / 4	2026-02-27
0.3.11	6 / 4	2026-02-18
0.3.10	6 / 4	2026-02-18
0.3.8	6 / 4	2026-02-13
0.3.7	6 / 4	2026-02-13
0.3.5	6 / 4	2026-02-11
0.3.4	5 / 4	2026-02-11
0.3.3	5 / 4	2026-02-11
0.1.1	4 / 4	2026-02-09
0.1.0	4 / 4	2026-02-09

v0.3.76

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.75

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.63

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.62

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.61

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.60

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.59

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.57

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.55

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.54

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.53

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.52

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.50

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.49

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.46

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.45

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.44

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.41

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.40

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.39

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.38

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.37

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.35

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.33

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.29

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.28

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.27

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.26

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.24

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.23

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.20

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.18

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.js

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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.1.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.1.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.