@nsshunt/stsfhirpg
STS FHIR Postgres (pg) Persistence
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:xxhash-wasm | AI (phantom-deps): xxhash-wasm is declared in dependencies and likely used transitively or via dynamic import. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.2.38 | 11 / 14 | |
| 1.2.37 | 11 / 14 | |
| 1.2.36 | 11 / 14 | |
| 1.2.34 | 11 / 14 |
v1.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.