@roj-ai/sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Fires in test file saving/restoring process.env — standard test pattern, not a secret leak. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used in filesystem plugin to decode file content for writing — legitimate and expected use. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared dependency likely used transitively or via dynamic import in transport layer. | ai | |
| phantom-deps | phantom-dep:@hono/zod-validator | AI (phantom-deps): Declared dep likely used in HTTP transport layer; phantom-dep heuristic misses indirect usage patterns. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.1.22 | 8 / 3 | |
| 0.1.21 | 8 / 3 | |
| 0.1.20 | 8 / 3 | |
| 0.1.19 | 8 / 3 | |
| 0.1.18 | 8 / 3 | |
| 0.1.17 | 8 / 3 | |
| 0.1.16 | 8 / 3 | |
| 0.1.15 | 8 / 3 | |
| 0.1.14 | 8 / 3 | |
| 0.1.13 | 8 / 3 | |
| 0.1.12 | 8 / 3 | |
| 0.1.11 | 8 / 3 | |
| 0.1.10 | 8 / 3 | |
| 0.1.9 | 8 / 3 | |
| 0.1.8 | 8 / 3 | |
| 0.1.7 | 8 / 3 | |
| 0.1.6 | 8 / 3 | |
| 0.1.5 | 8 / 3 | |
| 0.1.4 | 8 / 3 | |
| 0.1.3 | 8 / 3 | |
| 0.1.1 | 8 / 3 | |
| 0.0.2 | 8 / 3 |
v0.1.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
4 findingsSpreading entire process.env into an object — may capture all secrets 5 | describe('config', () => { 6 | describe('loadConfig', () => { > 7 | const originalEnv = { ...process.env } 8 | 9 | afterEach(() => {
Spreading entire process.env into an object — may capture all secrets 36 | maxBuffer: 50 * 1024 * 1024, 37 | cwd: options?.cwd, > 38 | env: options?.env ? { ...process.env, ...options.env } : undefined, 39 | }) 40 | }
Spreading entire process.env into an object — may capture all secrets 198 | const child = this.processRunner.spawn(shell, [shellFlag, command], { 199 | cwd, > 200 | env: { ...process.env, ...config.env, PORT: String(port) }, 201 | detached: true, 202 | stdio: ['ignore', 'pipe', 'pipe'],
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.