@joggr/cli SEE LICENSE IN LICENSE.md 52 versions

@joggr/cli

npm Repository Homepage

CLI for Joggr - The context engineering toolkit for developing with AI agents

52

Versions

SEE LICENSE IN LICENSE.md

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

zrosenbauerdanielbot

Keywords

agentsaiclicontextdocumentationjoggrtoolkit

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:joi	AI (typosquat): @joggr/cli is a scoped CLI package for the Joggr platform; the name derives from the company brand, not an attempt to impersonate the 'joi' validation library.	ai	2026/04/25
phantom-deps	phantom-dep:open	AI (phantom-deps): Compiled CLI that ships prebuilt platform binaries via optional deps; runtime deps may be bundled into binaries and not directly imported in JS source.	ai	2026/04/25
phantom-deps	phantom-dep:pino	AI (phantom-deps): Same as above — bundled into compiled binary; not a phantom dep in the malicious sense.	ai	2026/04/25
phantom-deps	phantom-dep:picomatch	AI (phantom-deps): Same as above — bundled into compiled binary; not a phantom dep in the malicious sense.	ai	2026/04/25
phantom-deps	phantom-dep:global-directory	AI (phantom-deps): Same as above — bundled into compiled binary; not a phantom dep in the malicious sense.	ai	2026/04/25
phantom-deps	phantom-dep:package-manager-detector	AI (phantom-deps): Same as above — bundled into compiled binary; not a phantom dep in the malicious sense.	ai	2026/04/25

Versions (showing 52 of 52)

Version	Deps	Published
0.14.3	5 / 35	2026-04-28
0.14.2	5 / 35	2026-04-28
0.13.0	5 / 34	2026-04-24
0.12.1	5 / 34	2026-04-22
0.12.0	5 / 34	2026-04-20
0.11.7	5 / 34	2026-04-20
0.11.6	5 / 34	2026-04-18
0.11.5	5 / 34	2026-04-16
0.11.4	5 / 34	2026-04-16
0.11.3	5 / 34	2026-04-16
0.11.2	4 / 33	2026-04-16
0.11.1	3 / 32	2026-04-15
0.11.0	3 / 32	2026-04-15
0.10.4	3 / 30	2026-04-13
0.10.3	3 / 30	2026-04-13
0.10.2	3 / 30	2026-04-13
0.10.1	3 / 30	2026-04-10
0.10.0	3 / 30	2026-04-10
0.9.3	3 / 30	2026-04-09
0.9.2	3 / 30	2026-04-09
0.9.1	3 / 30	2026-04-09
0.9.0	3 / 30	2026-04-09
0.8.2	3 / 30	2026-04-09
0.8.1	3 / 30	2026-04-09
0.8.0	3 / 30	2026-04-08
0.7.7	2 / 29	2026-04-07
0.7.6	2 / 29	2026-04-07
0.7.5	2 / 29	2026-04-07
0.7.4	2 / 29	2026-04-07
0.7.3	2 / 29	2026-04-07
0.7.2	2 / 29	2026-04-07
0.7.1	1 / 29	2026-04-06
0.7.0	1 / 29	2026-04-03
0.6.5	0 / 26	2026-03-31
0.6.4	0 / 26	2026-03-31
0.6.3	0 / 27	2026-03-31
0.6.2	0 / 28	2026-03-30
0.6.1	0 / 28	2026-03-30
0.6.0	0 / 27	2026-03-30
0.5.1	0 / 27	2026-03-28
0.5.0	0 / 27	2026-03-27
0.4.2	0 / 27	2026-03-27
0.4.1	0 / 27	2026-03-27
0.4.0	0 / 27	2026-03-27
0.3.5	0 / 27	2026-03-26
0.3.4	0 / 27	2026-03-26
0.3.2	0 / 27	2026-03-26
0.3.1	0 / 27	2026-03-26
0.3.0	0 / 27	2026-03-26
0.2.1	0 / 15	2026-03-24
0.2.0	0 / 15	2026-03-24
0.1.0	4 / 5	2026-03-11

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.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.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.7

1 finding

LOW No provenance attestation provenance

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

v0.11.6

1 finding

LOW No provenance attestation provenance

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

v0.11.5

1 finding

LOW No provenance attestation provenance

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

v0.11.4

1 finding

LOW No provenance attestation provenance

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

v0.11.3

1 finding

LOW No provenance attestation provenance

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

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.4

1 finding

LOW No provenance attestation provenance

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

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.7

1 finding

LOW No provenance attestation provenance

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

v0.7.6

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.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.3.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.3.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.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.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.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.