@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/goal-store-C_Z3P5Cg.js | AI (source-diff): Rolldown-bundled ESM output; samples show goal store CRUD 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/session-MBebUrjk.js | AI (source-diff): Rolldown-bundled ESM output; samples show session management logic, not obfuscation. | 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 | |
| phantom-deps | phantom-dep:log4js | AI (phantom-deps): Bundled dist; imports inlined by tsdown bundler, not directly visible as top-level imports. | ai | |
| phantom-deps | phantom-dep:lz-string | AI (phantom-deps): lz-string is visibly used in the bundled dist for session-storage compression. | 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 | |
| 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:ajv | 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:zod | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.9.2 | 12 / 5 | |
| 0.9.1 | 12 / 5 | |
| 0.9.0 | 12 / 5 | |
| 0.5.0 | 12 / 6 | |
| 0.2.4 | 10 / 5 | |
| 0.2.3 | 10 / 5 | |
| 0.2.0 | 10 / 5 | |
| 0.1.2 | 10 / 5 | |
| 0.1.1 | 10 / 5 | |
| 0.1.0 | 10 / 5 |
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.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.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.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.