@claudebernard/prescription-alerts-element No license 45 versions

@claudebernard/prescription-alerts-element

npm

45

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-componentstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@lit-labs/signals	AI (phantom-deps): Lit framework extension; config-referenced.	ai	2026/05/29
phantom-deps	phantom-dep:tctx	AI (phantom-deps): Config-referenced dependency; stable for this package type.	ai	2026/05/29
phantom-deps	phantom-dep:playwright	AI (phantom-deps): Test tooling referenced in config; stable pattern.	ai	2026/05/29
phantom-deps	phantom-dep:@lit/localize	AI (phantom-deps): Lit framework plugin; config-referenced and stable.	ai	2026/05/29
phantom-deps	phantom-dep:he	AI (phantom-deps): Lit component with config-referenced and framework-loaded deps; stable pattern.	ai	2026/05/29
phantom-deps	phantom-dep:@claudebernard/fhir-mapper	AI (phantom-deps): Same org scope; likely loaded by convention or bundled, not a real phantom dep concern.	ai	2026/05/27
phantom-deps	phantom-dep:@types/fhir	AI (phantom-deps): Type-only package; framework-scoped, not a runtime phantom dep risk.	ai	2026/05/27
bogus-package	bogus-package	AI (bogus-package): Internal healthcare org package; missing repo/homepage is consistent with private-to-public publishing pattern, not spam.	ai	2026/05/27

Versions (showing 45 of 45)

Version	Deps	Published
1.2.0	8 / 34	2026-06-05
1.1.9	8 / 32	2026-06-02
1.1.8	8 / 32	2026-06-02
1.1.7	8 / 32	2026-06-02
1.1.6	8 / 32	2026-06-01
1.1.5	8 / 32	2026-06-01
1.1.4	8 / 32	2026-06-01
1.1.3	8 / 32	2026-06-01
1.1.2	8 / 32	2026-05-29
1.1.1	8 / 32	2026-05-29
1.1.0	8 / 32	2026-05-29
1.0.4	8 / 32	2026-05-26
1.0.3	8 / 32	2026-05-26
1.0.1	8 / 32	2026-05-19
1.0.0	8 / 32	2026-04-29
0.16.6	8 / 28	2026-03-18
0.16.5	8 / 28	2026-03-17
0.16.4	8 / 28	2026-03-10
0.16.3	8 / 28	2026-03-06
0.16.2	8 / 28	2026-03-06
0.16.1	8 / 28	2026-03-05
0.16.0	8 / 28	2026-03-05
0.15.3	8 / 28	2026-02-24
0.15.2	8 / 28	2026-02-18
0.15.1	8 / 28	2026-01-27
0.15.0	8 / 28	2026-01-27
0.14.1	8 / 28	2026-01-21
0.14.0	8 / 28	2026-01-20
0.13.1	8 / 28	2026-01-13
0.13.0	8 / 28	2026-01-13
0.12.0	8 / 28	2025-12-29
0.11.0	8 / 28	2025-12-23
0.10.1	7 / 28	2025-12-12
0.10.0	7 / 28	2025-12-12
0.9.1	7 / 28	2025-12-04
0.9.0	7 / 28	2025-12-02
0.8.0	7 / 28	2025-11-24
0.7.3	7 / 28	2025-11-17
0.7.2	7 / 28	2025-11-17
0.7.1	7 / 28	2025-11-17
0.7.0	7 / 28	2025-11-14
0.6.4	5 / 29	2025-11-06
0.6.3	5 / 29	2025-11-06
0.6.2	6 / 29	2025-11-04
0.6.1	6 / 29	2025-11-04

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.9

1 finding

LOW No provenance attestation provenance

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

v1.1.8

1 finding

LOW No provenance attestation provenance

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

v1.1.7

1 finding

LOW No provenance attestation provenance

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

v1.1.6

1 finding

LOW No provenance attestation provenance

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

v1.1.5

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.4

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.

v1.0.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.

v1.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.

v1.0.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.16.6

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.16.5

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.16.4

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.16.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.16.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.16.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.16.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.15.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.15.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.15.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.15.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.14.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.14.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.13.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.13.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.12.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.11.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.10.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.10.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.9.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.9.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.8.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.7.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.7.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.7.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.7.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.6.4

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.6.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.6.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.6.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.