@agentoctopus/gateway
AgentOctopus gateways: Slack, Discord, Telegram bots and agent-to-agent HTTP protocol
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): ws is a canonical, widely-trusted WebSocket library; addition is consistent with gateway functionality. | ai | |
| dependencies | unvetted-dep:telegraf | AI (dependencies): telegraf is the canonical Telegram bot library; expected dependency for a multi-platform bot gateway. | ai | |
| provenance | no-provenance | AI (provenance): No CI/CD provenance is common for small org packages; not a security risk on its own. | ai | |
| phantom-deps | phantom-dep:@agentoctopus/adapters | AI (phantom-deps): Same-org sibling package; likely re-exported rather than directly imported in source. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 10 / 6 | |
| 0.6.0 | 9 / 6 | |
| 0.5.18 | 9 / 6 | |
| 0.5.17 | 9 / 6 | |
| 0.5.12 | 9 / 6 | |
| 0.5.11 | 9 / 6 | |
| 0.5.8 | 9 / 6 | |
| 0.5.7 | 9 / 6 | |
| 0.5.6 | 9 / 6 | |
| 0.5.5 | 9 / 6 | |
| 0.5.3 | 9 / 6 | |
| 0.5.2 | 9 / 6 | |
| 0.5.1 | 9 / 6 | |
| 0.5.0 | 9 / 6 | |
| 0.4.3 | 9 / 6 | |
| 0.4.2 | 9 / 6 | |
| 0.4.1 | 9 / 6 | |
| 0.4.0 | 9 / 6 | |
| 0.3.4 | 9 / 6 | |
| 0.3.3 | 9 / 6 | |
| 0.3.1 | 8 / 6 | |
| 0.3.0 | 8 / 6 | |
| 0.2.1 | 8 / 6 | |
| 0.1.1 | 8 / 6 | |
| 0.1.0 | 8 / 6 |
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
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.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.