@jay-framework/jay-stack-cli Apache-2.0 40 versions

@jay-framework/jay-stack-cli

npm

40

Versions

Apache-2.0

License

No

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

yoavnoamsi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New dep is same-org @jay-framework scoped package, version-pinned to match this release; consistent with monorepo expansion.	ai	2026/05/19
bogus-package	bogus-package	AI (bogus-package): Monorepo CLI package from established publisher with 86 approved packages; sparse metadata is a style choice, not a spam indicator.	ai	2026/04/30
npm-metadata	no-description	AI (npm-metadata): Consistent across all versions of this monorepo package; not a malware signal.	ai	2026/04/30
phantom-deps	phantom-dep:vite	AI (phantom-deps): vite is used in build scripts (vite build) and as a runtime dep for dev server; phantom-dep heuristic misfires here.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/plugin-validator	AI (phantom-deps): Same-org dep likely used indirectly via framework internals; stable false positive for this monorepo package.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/fullstack-component	AI (phantom-deps): Same-org dep likely used indirectly; stable false positive for this monorepo package.	ai	2026/04/30

Versions (showing 40 of 40)

Version	Deps	Published
0.18.0	17 / 9	2026-06-06
0.17.4	17 / 9	2026-05-24
0.17.3	17 / 9	2026-05-15
0.17.2	17 / 9	2026-05-14
0.17.1	17 / 9	2026-05-14
0.17.0	17 / 9	2026-05-14
0.16.5	16 / 9	2026-05-10
0.16.4	16 / 9	2026-05-07
0.16.3	16 / 9	2026-04-30
0.16.2	16 / 9	2026-04-29
0.16.1	16 / 9	2026-04-27
0.16.0	16 / 9	2026-04-26
0.15.6	16 / 9	2026-04-15
0.15.5	16 / 9	2026-04-08
0.15.4	16 / 9	2026-03-31
0.15.3	16 / 9	2026-03-30
0.15.2	16 / 9	2026-03-27
0.15.1	16 / 9	2026-03-25
0.15.0	15 / 9	2026-03-25
0.14.0	14 / 9	2026-03-21
0.13.0	14 / 9	2026-02-18
0.12.0	14 / 9	2026-02-09
0.11.0	10 / 9	2026-01-26
0.10.0	7 / 9	2026-01-04
0.9.0	4 / 9	2025-12-02
0.8.0	4 / 9	2025-11-16
0.7.0	4 / 9	2025-11-10
0.6.9	4 / 9	2025-07-24
0.6.8	4 / 9	2025-07-24
0.6.7	4 / 9	2025-07-23
0.6.5	4 / 9	2025-07-21
0.6.4	4 / 9	2025-07-15
0.6.3	4 / 9	2025-07-09
0.6.2	4 / 9	2025-07-08
0.6.1	4 / 9	2025-07-07
0.6.0	3 / 9	2025-07-06
0.5.3	3 / 9	2025-07-01
0.5.2	3 / 9	2025-07-01
0.5.1	3 / 9	2025-07-01
0.5.0	3 / 9	2025-06-29

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.4

1 finding

LOW No provenance attestation provenance

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

v0.17.3

1 finding

LOW No provenance attestation provenance

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

v0.17.2

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.5

1 finding

LOW No provenance attestation provenance

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

v0.16.4

1 finding

LOW No provenance attestation provenance

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

v0.16.3

1 finding

LOW No provenance attestation provenance

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

v0.16.2

1 finding

LOW No provenance attestation provenance

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

v0.16.1

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.6

1 finding

LOW No provenance attestation provenance

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

v0.15.5

1 finding

LOW No provenance attestation provenance

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

v0.15.4

1 finding

LOW No provenance attestation provenance

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

v0.15.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.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

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.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.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.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.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.8.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.7.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.6.9

1 finding

LOW No provenance attestation provenance

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

v0.6.8

1 finding

LOW No provenance attestation provenance

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

v0.6.7

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

1 finding

LOW No provenance attestation provenance

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

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