@onlineapps/conn-orch-orchestrator
Workflow orchestration connector for OA Drive - handles message routing and workflow execution
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@onlineapps/conn-infra-mq | AI (phantom-deps): Internal org dependency; likely transitive import via other declared deps. | ai | |
| phantom-deps | phantom-dep:@onlineapps/conn-orch-cookbook | AI (phantom-deps): Internal org dependency; likely transitive import via other declared deps. | ai | |
| phantom-deps | phantom-dep:@onlineapps/conn-orch-registry | AI (phantom-deps): Internal org dependency; likely transitive import via other declared deps. | ai | |
| phantom-deps | phantom-dep:@onlineapps/conn-base-monitoring | AI (phantom-deps): Internal org dependency; likely transitive import via other declared deps. | ai | |
| phantom-deps | phantom-dep:@onlineapps/conn-orch-api-mapper | AI (phantom-deps): Internal org dependency; likely transitive import via other declared deps. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 1.0.15 | 5 / 3 | |
| 1.0.14 | 5 / 3 | |
| 1.0.13 | 5 / 3 | |
| 1.0.10 | 5 / 3 | |
| 1.0.9 | 5 / 3 | |
| 1.0.8 | 5 / 3 | |
| 1.0.7 | 5 / 3 | |
| 1.0.6 | 5 / 3 | |
| 1.0.5 | 5 / 3 | |
| 1.0.4 | 5 / 3 | |
| 1.0.3 | 5 / 3 | |
| 1.0.2 | 5 / 3 |
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.