@inkeep/create-agents
Create an Inkeep Agent Framework project
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Org migrated to GitHub Actions CI publishing with SLSA attestation; consistent pattern for this package family. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal accompanies org-wide shift to automated CI publishing; not indicative of takeover. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): CLI scaffolding tool; deps referenced in generated project templates, not direct imports. | ai | |
| phantom-deps | phantom-dep:drizzle-kit | AI (phantom-deps): CLI scaffolding tool; deps referenced in generated project templates, not direct imports. | ai | |
| phantom-deps | phantom-dep:@hono/zod-openapi | AI (phantom-deps): CLI scaffolding tool; deps referenced in generated project templates, not direct imports. | ai | |
| dependencies | unvetted-dep:@inkeep/agents-core | AI (dependencies): First-party Inkeep monorepo dependency; same publisher, same version pin, expected coupling. | ai |
Versions (showing 7 of 310)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 5 / 6 | |
| 0.2.0 | 4 / 5 | |
| 0.1.10 | 4 / 5 | |
| 0.1.9 | 4 / 5 | |
| 0.1.8 | 2 / 4 | |
| 0.1.7 | 2 / 4 | |
| 0.1.6 | 2 / 4 |
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.