@atomic-ehr/fhirpath
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Implements FHIRPath decode() function; not obfuscation or payload hiding. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Implements FHIRPath decode() function; not obfuscation or payload hiding. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): fast-xml-parser is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 4 / 20 | |
| 0.1.3 | 4 / 20 | |
| 0.1.2 | 4 / 20 | |
| 0.1.1 | 4 / 20 | |
| 0.1.0 | 4 / 20 | |
| 0.0.5 | 4 / 20 | |
| 0.0.4 | 4 / 20 | |
| 0.0.3 | 3 / 17 | |
| 0.0.2 | 3 / 13 | |
| 0.0.1 | 3 / 13 |
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.2
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.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.