@gencode/agents
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/builtin-provider-Zyp3W8uT.js | AI (source-diff): Rolldown bundle output; minified but readable, no malicious patterns. Stable for this package's build toolchain. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-DweGOw8P.js | AI (source-diff): File is a rolldown-bundled ESM output with readable logic; long lines are from minification, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/session-CpVlUp8c.js | AI (source-diff): Rolldown bundler output; code is readable minified ESM with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/goal-store-DvL6FpJV.js | AI (source-diff): Rolldown bundler output; code is readable minified ESM with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-Dz2XUj1H.js | AI (source-diff): Rolldown bundler output; code is readable minified ESM with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-BX9aHHJK.js | AI (source-diff): Standard rollup/tsdown bundle output; code is readable and benign, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-muN6YtZb.js | AI (source-diff): File is rollup/tsdown bundle output (hashed chunk name, readable ESM logic); not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-CuBb3DYN.js | AI (source-diff): Rolldown/tsdown minified bundle output; readable logic in sample, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Used transitively via bundled dist; phantom-dep heuristic fires but dep is clearly used in bundle. | ai | |
| source-diff | obfuscated-file:dist/session-D9x-WDl8.js | AI (source-diff): Rolldown/tsdown minified bundle output; readable session management logic in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/goal-store-C_oLLqTK.js | AI (source-diff): Rolldown/tsdown minified bundle output; readable goal-store logic in sample, no malicious patterns. | ai | |
| phantom-deps | phantom-dep:@types/better-sqlite3 | AI (phantom-deps): Type-only package; not directly imported at runtime by design. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-DVFQMfYl.js | AI (source-diff): Rolldown bundler output; minified but readable file I/O logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/goal-store-1Lewl_Xz.js | AI (source-diff): Rolldown bundler output; goal store logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/session-B26JETSt.js | AI (source-diff): Rolldown bundler output; session management logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/session-BDGOSbwC.js | AI (source-diff): Rolldown-bundled ESM output; content is readable session management logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-CXE7L9HO.js | AI (source-diff): Rolldown-bundled ESM output; content is readable file/memory management logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/goal-store-B36KsoVO.js | AI (source-diff): Rolldown-bundled ESM output; content is readable goal-store logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-DMxBOIZn.js | AI (source-diff): Rolldown bundle output; readable logic with node: imports, no obfuscation or malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-Bhzb_o53.js | AI (source-diff): Rolldown bundler output; code is readable minified ESM with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/session-CiekMEUQ.js | AI (source-diff): Rolldown bundler output; session management logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/goal-store-DxaeZmiE.js | AI (source-diff): Rolldown bundler output; goal store file I/O logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-PIpf9WYR.js | AI (source-diff): Rolldown-bundled ESM output; samples show legitimate file I/O and session logic, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/session-MBebUrjk.js | AI (source-diff): Rolldown-bundled ESM output; samples show session management logic, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@huggingface/transformers | AI (phantom-deps): ML library used via config/peer pattern in an AI agents package; phantom-dep is a false positive here. | ai | |
| source-diff | obfuscated-file:dist/goal-store-C_Z3P5Cg.js | AI (source-diff): Rolldown-bundled ESM output; samples show goal store CRUD logic, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-_CdSlTJE.js | AI (source-diff): Standard rollup/tsdown bundle output; sample shows readable ESM logic, not obfuscation. | ai | |
| phantom-deps | phantom-dep:lz-string | AI (phantom-deps): lz-string is visibly used in the bundled dist for session-storage compression. | ai | |
| phantom-deps | phantom-dep:log4js | AI (phantom-deps): Bundled dist; imports inlined by tsdown bundler, not directly visible as top-level imports. | ai | |
| source-diff | obfuscated-file:dist/builtin-provider-Bv7sulLa.js | AI (source-diff): Rolldown-generated bundle with readable code; long lines are minified but not obfuscated. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:isbinaryfile | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:gray-matter | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sqlite-vec | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.10.9 | 12 / 5 | |
| 0.10.8 | 12 / 5 | |
| 0.10.7 | 12 / 5 | |
| 0.10.6 | 12 / 5 | |
| 0.10.4 | 12 / 5 | |
| 0.10.3 | 12 / 5 | |
| 0.10.2 | 12 / 5 | |
| 0.10.1 | 12 / 5 | |
| 0.10.0 | 12 / 5 | |
| 0.9.3 | 12 / 5 | |
| 0.9.2 | 12 / 5 | |
| 0.9.1 | 12 / 5 | |
| 0.9.0 | 12 / 5 | |
| 0.8.3 | 11 / 5 | |
| 0.8.2 | 11 / 5 | |
| 0.8.1 | 11 / 5 | |
| 0.8.0 | 11 / 5 | |
| 0.7.7 | 11 / 5 | |
| 0.7.6 | 11 / 5 | |
| 0.7.5 | 11 / 5 | |
| 0.7.4 | 11 / 5 | |
| 0.7.3 | 11 / 5 | |
| 0.7.2 | 11 / 5 | |
| 0.7.1 | 13 / 5 | |
| 0.7.0 | 13 / 5 | |
| 0.6.2 | 11 / 5 | |
| 0.6.1 | 11 / 5 | |
| 0.6.0 | 11 / 5 | |
| 0.5.0 | 12 / 6 | |
| 0.4.0 | 11 / 5 | |
| 0.3.2 | 11 / 5 | |
| 0.3.1 | 11 / 5 | |
| 0.3.0 | 11 / 5 | |
| 0.2.4 | 10 / 5 | |
| 0.2.3 | 10 / 5 | |
| 0.2.2 | 10 / 5 | |
| 0.2.1 | 10 / 5 | |
| 0.2.0 | 10 / 5 | |
| 0.1.2 | 10 / 5 | |
| 0.1.1 | 10 / 5 | |
| 0.1.0 | 10 / 5 |
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.7.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.