@jay-framework/compiler-analyze-exported-types Apache-2.0 42 versions

@jay-framework/compiler-analyze-exported-types

npm

42

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
phantom-deps	phantom-dep:js-yaml	AI (phantom-deps): Monorepo build tool pattern; deps declared for downstream consumers, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:pluralize	AI (phantom-deps): Same monorepo pattern; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:change-case	AI (phantom-deps): Same monorepo pattern; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@types/js-yaml	AI (phantom-deps): Type-only dep; framework-scoped, stable false positive.	ai	2026/04/30
phantom-deps	phantom-dep:node-html-parser	AI (phantom-deps): Same monorepo pattern; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/secure	AI (phantom-deps): Same org scope; monorepo peer dependency pattern.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/runtime	AI (phantom-deps): Same org scope; monorepo peer dependency pattern.	ai	2026/04/30
phantom-deps	phantom-dep:@jay-framework/component	AI (phantom-deps): Same org scope; monorepo peer dependency pattern.	ai	2026/04/30

Versions (showing 42 of 42)

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

v0.18.2

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

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