@a5c-ai/babysitter-sdk
Storage and run-registry primitives for event-sourced babysitter workflows.
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 | net-exec-file:dist/harness/agenticTools.js | AI (source-diff): Compiled TS output for an AI agent tool SDK; network+exec is the intended functionality of the agentic tools layer. | ai | |
| source-diff | net-exec-file:dist/harness/piWrapper.js | AI (source-diff): Pi coding agent wrapper; network+exec is core to the package's documented agent session management. | ai | |
| phantom-deps | phantom-dep:@agentsh/secure-sandbox | AI (phantom-deps): Likely dynamically loaded in agent harness; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mariozechner/pi-coding-agent | AI (phantom-deps): Dynamically loaded Pi agent dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@a5c-ai/babysitter-breakpoints | AI (phantom-deps): Same-org dep; likely re-exported or used in compiled output. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| phantom-deps | phantom-dep:@a5c-ai/agent-catalog | AI (phantom-deps): Same org scope; likely used in compiled output or re-exported. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Major version bump (v0.0.182 → v5.0.0); package restructured to ship compiled dist/ only, explaining size drop. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| phantom-deps | phantom-dep:ulid | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): TypeScript monorepo; deps may be used transitively or via re-exports in compiled dist. | ai | |
| phantom-deps | phantom-dep:@a5c-ai/agent-mux | AI (phantom-deps): Same org scope; likely used in compiled output or re-exported. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 8 / 10 | |
| 0.0.187 | 6 / 8 | |
| 0.0.186 | 6 / 8 | |
| 0.0.185 | 6 / 8 | |
| 0.0.184 | 6 / 8 | |
| 0.0.183 | 6 / 8 | |
| 0.0.182 | 3 / 8 | |
| 0.0.181 | 2 / 8 | |
| 0.0.180 | 2 / 8 | |
| 0.0.179 | 2 / 8 | |
| 0.0.178 | 2 / 8 | |
| 0.0.177 | 2 / 8 | |
| 0.0.176 | 2 / 8 | |
| 0.0.175 | 2 / 8 | |
| 0.0.174 | 2 / 8 | |
| 0.0.173 | 2 / 8 | |
| 0.0.172 | 2 / 8 | |
| 0.0.171 | 2 / 8 | |
| 0.0.168 | 3 / 8 | |
| 0.0.167 | 3 / 8 | |
| 0.0.166 | 3 / 8 | |
| 0.0.165 | 3 / 8 | |
| 0.0.163 | 3 / 8 | |
| 0.0.158 | 3 / 8 | |
| 0.0.154 | 3 / 8 | |
| 0.0.152 | 3 / 8 | |
| 0.0.151 | 3 / 8 | |
| 0.0.150 | 3 / 8 | |
| 0.0.149 | 3 / 8 | |
| 0.0.148 | 3 / 8 | |
| 0.0.147 | 3 / 8 | |
| 0.0.144 | 3 / 8 | |
| 0.0.140 | 3 / 8 | |
| 0.0.139 | 3 / 8 | |
| 0.0.137 | 3 / 8 | |
| 0.0.78 | 3 / 8 | |
| 0.0.77 | 3 / 8 | |
| 0.0.76 | 3 / 8 | |
| 0.0.75 | 3 / 8 | |
| 0.0.70 | 3 / 8 | |
| 0.0.69 | 3 / 8 | |
| 0.0.68 | 3 / 8 | |
| 0.0.63 | 3 / 8 | |
| 0.0.62 | 3 / 8 | |
| 0.0.61 | 3 / 8 | |
| 0.0.60 | 3 / 8 | |
| 0.0.59 | 3 / 8 | |
| 0.0.58 | 3 / 8 | |
| 0.0.57 | 3 / 8 | |
| 0.0.56 | 3 / 8 | |
| 0.0.54 | 3 / 8 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.187
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.186
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.185
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.184
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.183
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.