← Home

@jay-framework/aiditor

npm

AIditor — visual AI-driven code editor plugin for Jay Framework

10
Versions
—
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.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/index.client.js AI (source-diff): Long encoded strings are base64 alphabet + Unicode trie data from bundled i18n/text libs; stable false positive for this package. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Zod is directly imported in source; heuristic false positive. ai
phantom-deps phantom-dep:busboy AI (phantom-deps): Busboy is directly imported in source; heuristic false positive. ai
phantom-deps phantom-dep:html2canvas AI (phantom-deps): html2canvas is directly imported in source; heuristic false positive. ai
phantom-deps phantom-dep:@jay-framework/stack-server-runtime AI (phantom-deps): Same-org scoped dependency; legitimate framework runtime. ai

Versions (showing 10 of 10)

Version Deps Published
0.18.0 7 / 8
0.17.4 7 / 8
0.17.3 7 / 8
0.17.2 7 / 8
0.17.1 7 / 8
0.17.0 7 / 8
0.16.5 7 / 8
0.16.4 7 / 7
0.16.3 7 / 7
0.16.2 7 / 7

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

2 findings
HIGH Long encoded string in modified file: dist/index.client.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.17.2

2 findings
HIGH Long encoded string in modified file: dist/index.client.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.17.1

2 findings
HIGH Long encoded string in modified file: dist/index.client.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.17.0

2 findings
HIGH Long encoded string in modified file: dist/index.client.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.16.5

2 findings
HIGH Long encoded string in modified file: dist/index.client.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

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

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