← Home

@relayauth/sdk

18
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

khaliqgantwillwashburn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): All instances are in test files asserting that scope-matching correctly rejects /etc/passwd paths. No actual file access occurs; this is a stable false positive for this package. ai

Versions (showing 18 of 18)

Version Deps Published
0.2.10 2 / 1
0.2.9 2 / 1
0.2.8 2 / 1
0.2.7 2 / 1
0.2.6 2 / 1
0.2.5 2 / 1
0.2.4 2 / 1
0.2.3 2 / 1
0.2.2 2 / 1
0.2.0 2 / 1
0.1.9 2 / 1
0.1.8 2 / 1
0.1.7 2 / 1
0.1.4 2 / 2
0.1.3 2 / 2
0.1.2 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2

v0.2.10

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.7

4 findings
HIGH etc-passwd-access: src/__tests__/scope-matcher.test.ts:61 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/AgentWorkforce/relayauth/blob/987066b3922fd5ffc22df7ac1c1a1b8530ed815a/src/__tests__/scope-matcher.test.ts#L61 59 | 60 | assert.equal( > 61 | matchScope("relayfile:fs:write:/etc/passwd", ["relayfile:fs:write:/src/*"]), 62 | false, 63 | );

HIGH etc-passwd-access: src/__tests__/scope-matcher.test.ts:137 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/AgentWorkforce/relayauth/blob/987066b3922fd5ffc22df7ac1c1a1b8530ed815a/src/__tests__/scope-matcher.test.ts#L137 135 | 136 | assert.throws( > 137 | () => matchScope("relayfile:fs:write:/src/../etc/passwd", ["relayfile:fs:write:/src/*"]), 138 | /\.\./, 139 | );

HIGH etc-passwd-access: src/__tests__/scope-matcher.test.ts:172 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/AgentWorkforce/relayauth/blob/987066b3922fd5ffc22df7ac1c1a1b8530ed815a/src/__tests__/scope-matcher.test.ts#L172 170 | ); 171 | assert.equal( > 172 | matchScope("relayfile:fs:read:/etc/passwd", ["relayfile:fs:read:/*"]), 173 | true, 174 | );

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

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.