@jay-framework/compiler-jay-stack
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a runtime dep used via vite/tsup build tooling; phantom-dep heuristic misfires for build-tool packages. | ai | |
| phantom-deps | phantom-dep:@jay-framework/compiler-shared | AI (phantom-deps): Same-org sibling; may be re-exported or used indirectly through @jay-framework/compiler. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal package; missing metadata is expected, not a spam/malware indicator. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 7 / 4 | |
| 0.17.4 | 7 / 4 | |
| 0.17.3 | 7 / 4 | |
| 0.17.2 | 7 / 4 | |
| 0.17.1 | 7 / 4 | |
| 0.17.0 | 7 / 4 | |
| 0.16.5 | 7 / 4 | |
| 0.16.4 | 7 / 4 | |
| 0.16.3 | 7 / 4 | |
| 0.16.2 | 7 / 4 | |
| 0.16.1 | 7 / 4 | |
| 0.16.0 | 7 / 4 | |
| 0.15.6 | 7 / 4 | |
| 0.15.5 | 7 / 4 | |
| 0.15.4 | 7 / 4 | |
| 0.15.3 | 7 / 4 | |
| 0.15.2 | 7 / 4 | |
| 0.15.1 | 7 / 4 | |
| 0.15.0 | 7 / 4 | |
| 0.14.0 | 7 / 4 | |
| 0.13.0 | 7 / 4 | |
| 0.12.0 | 7 / 4 | |
| 0.11.0 | 6 / 4 | |
| 0.10.0 | 6 / 4 | |
| 0.9.0 | 4 / 5 |
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.