@fhir-dsl/mcp
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is a low signal for this package; no other risk indicators present. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped FHIR DSL package; Levenshtein match to 'yup' is coincidental, not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:@fhir-dsl/core | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo peer packages. | ai | |
| phantom-deps | phantom-dep:@fhir-dsl/types | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo peer packages. | ai | |
| phantom-deps | phantom-dep:@fhir-dsl/runtime | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo peer packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.56.0 | 3 / 3 | |
| 0.55.0 | 3 / 3 | |
| 0.54.0 | 3 / 3 | |
| 0.53.0 | 3 / 3 | |
| 0.52.0 | 3 / 3 | |
| 0.51.0 | 3 / 3 | |
| 0.50.0 | 3 / 2 | |
| 0.49.0 | 3 / 2 | |
| 0.48.1 | 3 / 2 | |
| 0.48.0 | 3 / 2 | |
| 0.47.0 | 3 / 0 | |
| 0.46.0 | 3 / 0 | |
| 0.45.0 | 3 / 0 | |
| 0.44.0 | 3 / 0 | |
| 0.43.0 | 3 / 0 | |
| 0.42.1 | 3 / 0 | |
| 0.42.0 | 3 / 0 | |
| 0.41.0 | 3 / 0 |
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.