@claudebernard/shared-medication-review-element
An element providing some custom stuff.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/shared-medication-review-00KXBHS2.js | AI (source-diff): Vite-bundled dist output; long lines are minification, not obfuscation. Stable for this package. | ai | |
| source-diff | net-exec-file:dist/shared-medication-review-00KXBHS2.js | AI (source-diff): Bundled frontend component with fetch calls and dynamic patterns; expected for Lit web component dist. | ai | |
| source-diff | net-exec-file:dist/shared-medication-review-FvdGETFS.js | AI (source-diff): Network calls and dynamic code in a UI component bundle are expected (fetch API, dynamic imports); no dropper pattern visible in sample. | ai | |
| source-diff | obfuscated-file:dist/shared-medication-review-FvdGETFS.js | AI (source-diff): Standard Vite/Rollup minified bundle; readable identifiers, no encoded payloads. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:dist/shared-medication-review-XKwHQsYQ.js | AI (source-diff): Bundled frontend component using fetch + dynamic imports; expected pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/shared-medication-review-XKwHQsYQ.js | AI (source-diff): Vite bundle output with readable helper names; standard minified build artifact for this Lit web-component package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): graphql, graphql-ws, graphql-sse are established packages matching the project's GraphQL codegen toolchain. | ai | |
| source-diff | obfuscated-file:dist/sprite-SImp73Ku-SImp73Ku.js | AI (source-diff): Inlined SVG sprite sheet — long lines are SVG paths, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Deps moved to peerDeps and bundled inline; expected size increase. | ai | |
| source-diff | obfuscated-file:dist/shared-medication-review-Dl0cMDzj.js | AI (source-diff): Vite build output for Lit web component; readable preamble, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/shared-medication-review-Dl0cMDzj.js | AI (source-diff): Frontend bundle with fetch + dynamic patterns; standard for Lit/GraphQL web components. | ai | |
| dependencies | unvetted-dep:@types/he | AI (dependencies): @types/he is a benign TypeScript type definition for the 'he' HTML entity encoder; no security risk. | ai | |
| provenance | no-provenance | AI (provenance): Organizational package with consistent release history; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:@claudebernard/prescription-alerts-element | AI (phantom-deps): Sibling org package; same-scope phantom-dep is a known false positive pattern. | ai | |
| phantom-deps | phantom-dep:he | AI (phantom-deps): he is declared as a runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal healthcare org package; no repo URL and sparse README are consistent with private-to-public publishing pattern, not spam. | ai | |
| phantom-deps | phantom-dep:tctx | AI (phantom-deps): tctx declared as runtime dep; referenced in config files per analyzer note. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql declared as runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@types/he | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:graphql-ws | AI (phantom-deps): Declared runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@types/fhir | AI (phantom-deps): Type-only package; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:graphql-sse | AI (phantom-deps): Declared runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@lit/localize | AI (phantom-deps): Declared runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@lit-labs/signals | AI (phantom-deps): Declared runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:vite-tsconfig-paths | AI (phantom-deps): Build-time dep referenced in vite config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@hey-api/client-fetch | AI (phantom-deps): Declared runtime dep; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@claudebernard/side-effects-element | AI (phantom-deps): Sibling org package; same-scope phantom-dep is a known false positive pattern. | ai | |
| phantom-deps | phantom-dep:@claudebernard/patient-profile-element | AI (phantom-deps): Sibling org package; same-scope phantom-dep is a known false positive pattern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 13 / 39 | |
| 0.10.1 | 13 / 39 | |
| 0.9.0 | 13 / 39 | |
| 0.6.3 | 15 / 39 | |
| 0.6.2 | 15 / 39 | |
| 0.6.1 | 15 / 39 | |
| 0.4.0 | 13 / 39 | |
| 0.3.2 | 12 / 39 | |
| 0.3.1 | 12 / 39 | |
| 0.3.0 | 12 / 39 | |
| 0.2.1 | 9 / 35 | |
| 0.1.3 | 9 / 35 | |
| 0.1.1 | 9 / 35 | |
| 0.1.0 | 9 / 35 |
v0.11.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (acroquelois_pro) than the most recent previously approved version (admin_claudebernard) on 2026-04-27, but acroquelois_pro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.10.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (acroquelois_pro) than the most recent previously approved version (admin_claudebernard) on 2026-04-20, but acroquelois_pro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.9.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.