@indexnetwork/protocol
The agent orchestration layer for Index Network. Implements LangGraph-based workflows for intent processing, opportunity discovery, and chat — decoupled from any specific infrastructure via adapter injection.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is a declared dep used via --env-file flag in scripts, not directly imported in source; stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/opportunity/question.prompt.d.ts | AI (source-diff): Long lines are TypeScript type declarations with inline documentation, not obfuscated code. | ai | |
| provenance | no-provenance | AI (provenance): Common for npm packages; no other risk signals present to elevate this. | ai | |
| phantom-deps | phantom-dep:@langchain/langgraph-checkpoint-postgres | AI (phantom-deps): Declared as a runtime dep for optional postgres checkpoint backend; may be used indirectly or conditionally without direct import. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.24.1 | 7 / 2 | |
| 1.23.1 | 7 / 2 | |
| 1.9.1 | 7 / 2 | |
| 1.7.0 | 7 / 2 | |
| 1.5.1 | 7 / 2 | |
| 0.30.3 | 7 / 2 | |
| 0.30.1 | 7 / 2 | |
| 0.29.1 | 7 / 2 | |
| 0.28.8 | 7 / 2 | |
| 0.28.7 | 7 / 2 | |
| 0.28.6 | 7 / 2 | |
| 0.28.4 | 7 / 2 | |
| 0.28.3 | 7 / 2 | |
| 0.28.2 | 7 / 2 | |
| 0.28.0 | 7 / 2 | |
| 0.23.0 | 7 / 2 | |
| 0.22.0 | 7 / 2 | |
| 0.4.0 | 7 / 2 | |
| 0.3.3 | 7 / 2 | |
| 0.3.2 | 7 / 2 | |
| 0.3.1 | 7 / 2 | |
| 0.3.0 | 7 / 2 | |
| 0.2.1 | 7 / 2 | |
| 0.2.0 | 7 / 2 | |
| 0.1.0 | 7 / 2 |
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
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 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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.