@jay-framework/dev-server Apache-2.0 40 versions

@jay-framework/dev-server

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
bogus-package	bogus-package	AI (bogus-package): Monorepo internal package; no-repo and no-keywords are expected for framework components.	ai	2026/05/04
phantom-deps	phantom-dep:@jay-framework/compiler-shared	AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal framework packages.	ai	2026/05/04
phantom-deps	phantom-dep:@jay-framework/stack-client-runtime	AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal framework packages.	ai	2026/05/04
npm-metadata	no-description	AI (npm-metadata): Framework internal package; description omission is benign in monorepo context.	ai	2026/05/04
phantom-deps	phantom-dep:@jay-framework/runtime	AI (phantom-deps): Same-org monorepo dep; may be used transitively or via re-export pattern.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/component	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/view-state-merge	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/fullstack-component	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/30

Versions (showing 40 of 40)

Version	Deps	Published
0.18.0	12 / 15	2026-06-06
0.17.4	12 / 15	2026-05-24
0.17.3	12 / 15	2026-05-15
0.17.2	12 / 15	2026-05-14
0.17.1	12 / 15	2026-05-14
0.17.0	12 / 15	2026-05-14
0.16.5	12 / 15	2026-05-10
0.16.4	12 / 15	2026-05-07
0.16.3	12 / 15	2026-04-30
0.16.2	12 / 15	2026-04-29
0.16.1	12 / 15	2026-04-27
0.16.0	11 / 14	2026-04-26
0.15.6	11 / 14	2026-04-15
0.15.5	11 / 14	2026-04-08
0.15.4	11 / 14	2026-03-31
0.15.3	11 / 14	2026-03-30
0.15.2	11 / 14	2026-03-27
0.15.1	11 / 14	2026-03-25
0.15.0	11 / 14	2026-03-25
0.14.0	11 / 14	2026-03-21
0.13.0	11 / 11	2026-02-18
0.12.0	11 / 11	2026-02-09
0.11.0	10 / 11	2026-01-26
0.10.0	10 / 11	2026-01-04
0.9.0	9 / 11	2025-12-02
0.8.0	9 / 11	2025-11-16
0.7.0	9 / 11	2025-11-10
0.6.9	9 / 11	2025-07-24
0.6.8	9 / 11	2025-07-24
0.6.7	8 / 11	2025-07-23
0.6.5	8 / 11	2025-07-21
0.6.4	8 / 11	2025-07-15
0.6.3	7 / 11	2025-07-09
0.6.2	7 / 11	2025-07-08
0.6.1	7 / 11	2025-07-07
0.6.0	7 / 11	2025-07-06
0.5.3	7 / 11	2025-07-01
0.5.2	7 / 11	2025-07-01
0.5.1	7 / 11	2025-07-01
0.5.0	7 / 11	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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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