@atomic-ehr/fhir-canonical-manager
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): env spread used to override HOME for bun subprocess isolation; not a secret-capture pattern. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.0.24 | 0 / 4 | |
| 0.0.23 | 0 / 4 | |
| 0.0.22 | 0 / 4 | |
| 0.0.21 | 0 / 4 | |
| 0.0.20 | 0 / 4 | |
| 0.0.19 | 0 / 4 | |
| 0.0.18 | 0 / 4 | |
| 0.0.17 | 0 / 4 | |
| 0.0.16 | 0 / 4 | |
| 0.0.15 | 0 / 4 | |
| 0.0.14 | 0 / 4 | |
| 0.0.13 | 0 / 3 | |
| 0.0.12 | 0 / 3 | |
| 0.0.11 | 0 / 3 | |
| 0.0.10 | 0 / 3 | |
| 0.0.9 | 0 / 3 | |
| 0.0.8 | 0 / 3 | |
| 0.0.7 | 0 / 3 | |
| 0.0.6 | 0 / 3 | |
| 0.0.5 | 0 / 3 | |
| 0.0.4 | 0 / 3 | |
| 0.0.3 | 0 / 3 | |
| 0.0.2 | 0 / 3 |
v0.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.15
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/atomic-ehr/fhir-canonical-manager/blob/24ec3a3cdd762d2f64391b18e6d11e2b4e854a55/src/package.ts#L54 52 | if (packageManager === "bun") { 53 | // Use bun with auth bypass trick for FHIR registry > 54 | const env = { 55 | ...process.env, 56 | HOME: pwd, // Prevent reading user's .npmrc
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.14
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/atomic-ehr/fhir-canonical-manager/blob/39a82a519b53fb209f680920d34f4a5ea9513d34/src/package.ts#L54 52 | if (packageManager === "bun") { 53 | // Use bun with auth bypass trick for FHIR registry > 54 | const env = { 55 | ...process.env, 56 | HOME: pwd, // Prevent reading user's .npmrc
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.