@normahq/codex-acp-bridge SEE LICENSE IN LICENSE 14 versions

@normahq/codex-acp-bridge

npm Repository Homepage

Meta package for codex-acp-bridge

14

Versions

SEE LICENSE IN LICENSE

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

metalagman

Keywords

aillmcodexacpmcpagentbridgecli

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): Used to dispatch to platform-specific binary; standard pattern for this meta-package.	ai	2026/04/29

Versions (showing 14 of 14)

Version	Deps	Published
1.4.2	0 / 0	2026-05-07
1.4.1	0 / 0	2026-05-07
1.4.0	0 / 0	2026-05-07
1.3.0	0 / 0	2026-04-28
1.2.1	0 / 0	2026-04-27
1.2.0	0 / 0	2026-04-24
1.1.0	0 / 0	2026-04-24
1.0.2	0 / 0	2026-04-23
1.0.1	0 / 0	2026-04-22
1.0.0	0 / 0	2026-04-21
0.0.4	0 / 0	2026-04-20
0.0.3	0 / 0	2026-03-29
0.0.2	0 / 0	2026-03-27
0.0.1	0 / 0	2026-03-27

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.