← Home

@gencode/cli

npm
20
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

liangshuaijardenliu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/program-DoHYZho_.js AI (source-diff): Standard tsdown/rollup bundle output; imports are readable and benign. Not obfuscated, just minified. ai
source-diff obfuscated-file:dist/program-tnfIUw2v.js AI (source-diff): Standard tsdown/rollup bundle output; sample shows clean ESM imports with no malicious patterns. ai
phantom-deps phantom-dep:log4js AI (phantom-deps): log4js is directly imported in the bundle (import v from 'log4js'); phantom-dep is a false positive for bundled output. ai
phantom-deps phantom-dep:gensign-node AI (phantom-deps): gensign-node is imported in the bundle (import oe from 'gensign-node'); phantom-dep is a false positive for bundled output. ai
source-diff obfuscated-file:dist/program-B2JBui5b.js AI (source-diff): File is a standard tsdown/rollup ESM bundle with readable imports; not obfuscated or malicious. ai
source-diff obfuscated-file:dist/program-BYEa961T.js AI (source-diff): Standard tsdown/rollup bundle output; content is readable CLI logic, not malicious obfuscation. ai
bogus-package bogus-package AI (bogus-package): Early-stage monorepo CLI tool; missing metadata is consistent across all versions, not a spam indicator. ai
source-diff obfuscated-file:dist/program-CJPDK5S0.js AI (source-diff): Minified tsdown bundle output with readable imports; not obfuscation. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @gencode/cli is a scoped org package; Levenshtein match to 'joi' is coincidental, not a typosquat. ai
phantom-deps phantom-dep:@gencode/shared AI (phantom-deps): Same org scope; likely used indirectly or via config — stable false positive for this package. ai
phantom-deps phantom-dep:@gencode/agents AI (phantom-deps): Same org scope; likely used indirectly or via config — stable false positive for this package. ai

Versions (showing 20 of 20)

Version Deps Published
0.6.8 5 / 4
0.6.7 5 / 4
0.6.6 5 / 4
0.6.5 5 / 4
0.6.4 5 / 4
0.6.3 5 / 4
0.6.2 5 / 4
0.6.0 5 / 4
0.1.4 5 / 4
0.1.3 5 / 4
0.1.0 5 / 4
0.0.55 5 / 4
0.0.54 5 / 4
0.0.34 5 / 4
0.0.26 4 / 4
0.0.24 4 / 4
0.0.23 4 / 4
0.0.6 3 / 4
0.0.2 3 / 4
0.0.1 3 / 4

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

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.6

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.5

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.4

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.3

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.2

2 findings
HIGH New obfuscated file: dist/program-DoHYZho_.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.6.0

3 findings
HIGH New obfuscated file: dist/program-tnfIUw2v.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

INFO Publisher changed: liangshuai → jardenliu (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (jardenliu) than the most recent previously approved version (liangshuai) on 2026-05-27, but jardenliu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.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.1.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.1.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.0.55

1 finding
LOW No provenance attestation provenance

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

v0.0.54

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

2 findings
HIGH New obfuscated file: dist/program-B2JBui5b.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.26

2 findings
HIGH New obfuscated file: dist/program-CJPDK5S0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.24

2 findings
HIGH New obfuscated file: dist/program-BYEa961T.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.23

2 findings
HIGH New obfuscated file: dist/program-BYEa961T.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

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