← Home

@smals-belgium-shared/uhmep-prescription-details

npm Repository Homepage

Prescription details web component

6
Versions
SWCL License
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

jdsssmals

Keywords

web-componentangularprescription

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:build/wc-prescription-details.js AI (source-diff): Angular compiled bundle; long encoded strings are minified template/component metadata, not malicious payloads. ai

Versions (showing 6 of 6)

Version Deps Published
1.103.1 0 / 0
1.101.4 0 / 0
1.15.1 0 / 0
1.15.0 0 / 0
1.14.1 0 / 0
1.14.0 0 / 0

v1.103.1

1 finding
LOW No provenance attestation provenance

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

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

2 findings
HIGH Long encoded string in modified file: build/wc-prescription-details.js source-diff

Modified file contains 11 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.15.0

2 findings
HIGH Long encoded string in modified file: build/wc-prescription-details.js source-diff

Modified file contains 11 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.14.1

1 finding
LOW No provenance attestation provenance

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

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