@grackle-ai/powerline
gRPC PowerLine server for Grackle AI agent integration
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): New deps are same-org first-party packages pinned to the same version; not a supply-chain injection risk. | ai | |
| dependencies | unvetted-dep:@grackle-ai/ahp | AI (dependencies): First-party sibling package from same monorepo/publisher; versioned in lockstep. | ai | |
| dependencies | unvetted-dep:@grackle-ai/ahp-transport | AI (dependencies): First-party sibling package from same monorepo/publisher; versioned in lockstep. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared runtime dependency; phantom-dep is a false positive for this package. | ai |
Versions (showing 51 of 148)
| Version | Deps | Published |
|---|---|---|
| 0.143.0 | 15 / 6 | |
| 0.142.0 | 15 / 6 | |
| 0.138.0 | 15 / 6 | |
| 0.135.1 | 13 / 5 | |
| 0.134.0 | 13 / 5 | |
| 0.133.0 | 13 / 5 | |
| 0.132.2 | 14 / 5 | |
| 0.132.1 | 14 / 5 | |
| 0.132.0 | 14 / 5 | |
| 0.131.0 | 14 / 4 | |
| 0.130.0 | 14 / 4 | |
| 0.129.0 | 14 / 4 | |
| 0.128.0 | 14 / 4 | |
| 0.127.0 | 14 / 4 | |
| 0.126.1 | 14 / 4 | |
| 0.126.0 | 14 / 4 | |
| 0.125.2 | 14 / 4 | |
| 0.125.1 | 14 / 4 | |
| 0.125.0 | 14 / 4 | |
| 0.124.0 | 14 / 4 | |
| 0.123.2 | 14 / 4 | |
| 0.123.1 | 14 / 4 | |
| 0.123.0 | 14 / 4 | |
| 0.122.0 | 14 / 4 | |
| 0.121.0 | 14 / 4 | |
| 0.120.0 | 14 / 4 | |
| 0.119.0 | 14 / 4 | |
| 0.118.0 | 14 / 4 | |
| 0.117.0 | 14 / 4 | |
| 0.116.0 | 14 / 4 | |
| 0.115.2 | 14 / 4 | |
| 0.115.1 | 14 / 4 | |
| 0.115.0 | 14 / 4 | |
| 0.114.0 | 14 / 4 | |
| 0.113.0 | 14 / 4 | |
| 0.112.2 | 14 / 4 | |
| 0.112.1 | 14 / 4 | |
| 0.112.0 | 14 / 4 | |
| 0.111.0 | 14 / 4 | |
| 0.110.3 | 14 / 4 | |
| 0.110.2 | 14 / 4 | |
| 0.110.1 | 14 / 4 | |
| 0.108.4 | 14 / 4 | |
| 0.108.3 | 14 / 4 | |
| 0.108.2 | 14 / 4 | |
| 0.108.1 | 14 / 4 | |
| 0.108.0 | 14 / 4 | |
| 0.107.2 | 14 / 4 | |
| 0.107.1 | 14 / 4 | |
| 0.107.0 | 14 / 4 | |
| 0.106.3 | 14 / 4 |
v0.143.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.138.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.135.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.134.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.132.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.132.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.132.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.130.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.129.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.128.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.127.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.126.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.125.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.124.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.123.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.123.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.123.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.122.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.115.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.115.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.112.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.112.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.110.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.107.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.107.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.106.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.