← Home

@claudebernard/patient-profile-element

npm
18
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gdrouettpoutrain_resipsclerboutclaudebernard_tcaillieracroquelois_proadmin_claudebernardclaudebernard_jhudelle

Keywords

claude-bernardweb-componentstypescriptfhir

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Internal/org package published without CI provenance; consistent across all 18 versions. ai
phantom-deps phantom-dep:he AI (phantom-deps): he is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:tctx AI (phantom-deps): tctx is a declared runtime dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@lit-labs/signals AI (phantom-deps): Declared runtime dep; phantom-dep false positive. ai
phantom-deps phantom-dep:vite-tsconfig-paths AI (phantom-deps): Build-time dep referenced in vite config; phantom-dep false positive. ai
phantom-deps phantom-dep:@lit/localize AI (phantom-deps): Declared runtime dep used in Lit i18n; phantom-dep false positive. ai
bogus-package bogus-package AI (bogus-package): Internal healthcare org package; sparse public metadata is expected for private-first packages. ai

Versions (showing 18 of 18)

Version Deps Published
0.5.2 6 / 38
0.5.1 6 / 38
0.5.0 6 / 38
0.4.3 6 / 38
0.4.2 6 / 38
0.4.0 6 / 36
0.3.5 6 / 36
0.3.4 6 / 36
0.3.3 6 / 36
0.3.2 6 / 36
0.3.1 6 / 36
0.3.0 6 / 36
0.2.0 6 / 36
0.1.4 6 / 36
0.1.3 6 / 36
0.1.2 6 / 36
0.1.1 6 / 36
0.0.1 6 / 36

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.2

2 findings
HIGH Publisher changed: claudebernard_tcaillier → admin_claudebernard (on 2026-01-14) provenance

This version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.