@inkeep/agents-manage-api
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/factory2.js | AI (source-diff): Bundled/minified build output (tsdown), not obfuscation; imports typed schema modules. | ai | |
| source-diff | net-exec-file:dist/factory2.js | AI (source-diff): API server bundle naturally combines network (hono) and dynamic code paths; no exfil behavior shown. | ai | |
| source-diff | net-exec-file:dist/chunk-AZCUT3UE.js | AI (source-diff): Bundled dependency code (hono/nango/composio clients), not a dropper; consistent with declared deps. | ai | |
| source-diff | net-exec-file:dist/chunk-3TUIAUTG.js | AI (source-diff): Bundled API server chunk (hono/drizzle/mcp/oauth libs), not a dropper; consistent with stated function. | ai | |
| source-diff | net-exec-file:dist/chunk-6E4QM6FE.js | AI (source-diff): Bundled server code (tsup output) for a large API package, not a dropper/loader. | ai | |
| source-diff | net-exec-file:dist/chunk-NMRIX6IG.js | AI (source-diff): Bundled output of legit new deps (openid-client/nango/composio), not injected loader code. | ai | |
| source-diff | net-exec-file:dist/chunk-7YBMBKBI.js | AI (source-diff): Bundled server code with legit API/OAuth imports matching declared deps, not a dropper. | ai | |
| source-diff | net-exec-file:dist/chunk-VM5BBJTO.js | AI (source-diff): Bundled tsup output of legitimate API route/schema code, not a dropper. | ai | |
| source-diff | net-exec-file:dist/chunk-BAMAX6LI.js | AI (source-diff): Bundled third-party SDK code (oauth/nango/composio), not an injected dropper. | ai | |
| phantom-deps | phantom-dep:@inkeep/agents-manage-mcp | AI (phantom-deps): Same-org sibling package. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Used via config/transitive wiring, common tsup bundling pattern. | ai | |
| source-diff | net-exec-file:dist/chunk-QKQOZRHG.js | AI (source-diff): Bundled tsup output containing app logic, not a loader/dropper. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Used via config/transitive wiring, common tsup bundling pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All additions are established, widely-used packages fitting the API framework's scope. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Server bootstrap dep, used indirectly. | ai | |
| phantom-deps | phantom-dep:@nangohq/types | AI (phantom-deps): Type-only usage typical for @types-like packages. | ai | |
| phantom-deps | phantom-dep:@composio/core | AI (phantom-deps): Config-referenced integration dep. | ai | |
| phantom-deps | phantom-dep:@nangohq/node | AI (phantom-deps): Config-referenced integration dep. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-file usage pattern, common for dotenv. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Used via hono-pino config, not a real issue. | ai |
Versions (showing 68 of 168)
| Version | Deps | Published |
|---|---|---|
| 0.19.5 | 14 / 10 | |
| 0.19.4 | 14 / 10 | |
| 0.19.3 | 14 / 10 | |
| 0.19.2 | 14 / 10 | |
| 0.19.1 | 14 / 10 | |
| 0.19.0 | 14 / 10 | |
| 0.18.1 | 14 / 10 | |
| 0.18.0 | 14 / 10 | |
| 0.17.0 | 14 / 10 | |
| 0.16.3 | 14 / 10 | |
| 0.16.2 | 14 / 10 | |
| 0.16.1 | 14 / 10 | |
| 0.16.0 | 14 / 10 | |
| 0.15.0 | 14 / 10 | |
| 0.14.16 | 14 / 10 | |
| 0.14.15 | 14 / 10 | |
| 0.14.14 | 14 / 10 | |
| 0.14.13 | 14 / 10 | |
| 0.14.12 | 14 / 10 | |
| 0.14.11 | 14 / 10 | |
| 0.14.10 | 14 / 10 | |
| 0.14.9 | 14 / 10 | |
| 0.14.8 | 14 / 10 | |
| 0.14.7 | 14 / 10 | |
| 0.14.6 | 14 / 10 | |
| 0.14.5 | 14 / 10 | |
| 0.14.3 | 14 / 10 | |
| 0.14.2 | 14 / 10 | |
| 0.14.1 | 14 / 10 | |
| 0.14.0 | 14 / 10 | |
| 0.13.0 | 14 / 10 | |
| 0.12.1 | 14 / 10 | |
| 0.12.0 | 14 / 10 | |
| 0.11.3 | 14 / 10 | |
| 0.11.2 | 14 / 10 | |
| 0.11.1 | 14 / 10 | |
| 0.11.0 | 14 / 10 | |
| 0.10.2 | 14 / 11 | |
| 0.10.1 | 14 / 11 | |
| 0.9.0 | 15 / 11 | |
| 0.8.7 | 15 / 11 | |
| 0.8.6 | 15 / 11 | |
| 0.8.5 | 15 / 11 | |
| 0.8.4 | 15 / 11 | |
| 0.8.3 | 15 / 11 | |
| 0.8.2 | 15 / 11 | |
| 0.8.1 | 15 / 11 | |
| 0.8.0 | 15 / 11 | |
| 0.7.2 | 15 / 11 | |
| 0.7.1 | 15 / 11 | |
| 0.7.0 | 15 / 11 | |
| 0.6.6 | 15 / 11 | |
| 0.6.5 | 15 / 11 | |
| 0.6.4 | 15 / 11 | |
| 0.6.0 | 15 / 11 | |
| 0.5.0 | 15 / 11 | |
| 0.3.0 | 15 / 11 | |
| 0.2.2 | 15 / 11 | |
| 0.2.1 | 15 / 11 | |
| 0.2.0 | 15 / 11 | |
| 0.1.10 | 15 / 11 | |
| 0.1.9 | 15 / 11 | |
| 0.1.8 | 15 / 11 | |
| 0.1.7 | 15 / 11 | |
| 0.1.6 | 15 / 11 | |
| 0.1.2 | 16 / 11 | |
| 0.1.1 | 16 / 8 | |
| 0.1.0 | 16 / 8 |
v0.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.