@aporthq/aport-agent-guardrails-core

Core evaluator, passport, and config for APort agent guardrails (shared across frameworks)

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

uchi4jah

Keywords

aportagentguardrailsauthorizationpolicy

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:env-spread	AI (semgrep): Spreading process.env to pass it to a child process with an added variable is standard practice for this type of evaluator package.	ai	2026/05/02

Versions (showing 20 of 20)

Version	Deps	Published
1.0.29	1 / 6	2026-05-28
1.0.28	1 / 6	2026-05-28
1.0.27	1 / 6	2026-05-21
1.0.26	1 / 6	2026-05-05
1.0.25	1 / 6	2026-05-05
1.0.24	1 / 6	2026-04-29
1.0.23	1 / 6	2026-04-14
1.0.22	1 / 6	2026-04-13
1.0.21	1 / 6	2026-04-12
1.0.20	1 / 6	2026-03-26
1.0.18	1 / 6	2026-03-24
1.0.17	1 / 6	2026-03-22
1.0.15	1 / 6	2026-03-12
1.0.14	1 / 6	2026-03-11
1.0.13	1 / 6	2026-03-11
1.0.12	1 / 6	2026-03-02
1.0.11	1 / 6	2026-03-02
1.0.10	1 / 6	2026-02-20
1.0.9	1 / 6	2026-02-19
1.0.8	1 / 6	2026-02-19

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

1 finding

LOW No provenance attestation provenance

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

v1.0.25

1 finding

LOW No provenance attestation provenance

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

v1.0.24

3 findings

HIGH env-spread: src/core/evaluator.ts:116 semgrep

Spreading entire process.env into an object — may capture all secrets 114 | // Per-invocation decision file to avoid race when multiple tool calls run concurrently (Issue 1). 115 | const decisionPath = path.join(dataDir, `decision-${process.pid}-${Date.now()}.json`); > 116 | const env = { 117 | ...process.env, 118 | OPENCLAW_PASSPORT_FILE: passportPath,

HIGH env-spread: src/core/evaluator.ts:412 semgrep

Spreading entire process.env into an object — may capture all secrets 410 | `; 411 | const result = spawnSync(process.execPath, ['-e', script], { > 412 | env: { ...process.env, APORT_IN: tmpIn, APORT_OUT: tmpOut }, 413 | timeout: 15_000, 414 | encoding: 'utf8',

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.

v1.0.23

3 findings

HIGH env-spread: src/core/evaluator.ts:116 semgrep

Spreading entire process.env into an object — may capture all secrets 114 | // Per-invocation decision file to avoid race when multiple tool calls run concurrently (Issue 1). 115 | const decisionPath = path.join(dataDir, `decision-${process.pid}-${Date.now()}.json`); > 116 | const env = { 117 | ...process.env, 118 | OPENCLAW_PASSPORT_FILE: passportPath,

HIGH env-spread: src/core/evaluator.ts:412 semgrep

Spreading entire process.env into an object — may capture all secrets 410 | `; 411 | const result = spawnSync(process.execPath, ['-e', script], { > 412 | env: { ...process.env, APORT_IN: tmpIn, APORT_OUT: tmpOut }, 413 | timeout: 15_000, 414 | encoding: 'utf8',

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.

v1.0.22

3 findings

HIGH env-spread: src/core/evaluator.ts:116 semgrep

Spreading entire process.env into an object — may capture all secrets 114 | // Per-invocation decision file to avoid race when multiple tool calls run concurrently (Issue 1). 115 | const decisionPath = path.join(dataDir, `decision-${process.pid}-${Date.now()}.json`); > 116 | const env = { 117 | ...process.env, 118 | OPENCLAW_PASSPORT_FILE: passportPath,

HIGH env-spread: src/core/evaluator.ts:412 semgrep

Spreading entire process.env into an object — may capture all secrets 410 | `; 411 | const result = spawnSync(process.execPath, ['-e', script], { > 412 | env: { ...process.env, APORT_IN: tmpIn, APORT_OUT: tmpOut }, 413 | timeout: 15_000, 414 | encoding: 'utf8',

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.

v1.0.21

3 findings

HIGH env-spread: src/core/evaluator.ts:116 semgrep

Spreading entire process.env into an object — may capture all secrets 114 | // Per-invocation decision file to avoid race when multiple tool calls run concurrently (Issue 1). 115 | const decisionPath = path.join(dataDir, `decision-${process.pid}-${Date.now()}.json`); > 116 | const env = { 117 | ...process.env, 118 | OPENCLAW_PASSPORT_FILE: passportPath,

HIGH env-spread: src/core/evaluator.ts:412 semgrep

Spreading entire process.env into an object — may capture all secrets 410 | `; 411 | const result = spawnSync(process.execPath, ['-e', script], { > 412 | env: { ...process.env, APORT_IN: tmpIn, APORT_OUT: tmpOut }, 413 | timeout: 15_000, 414 | encoding: 'utf8',

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.

v1.0.20

1 finding

LOW No provenance attestation provenance

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

v1.0.18

1 finding

LOW No provenance attestation provenance

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

v1.0.17

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

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.

v1.0.9

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.

v1.0.8

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.