@claudebernard/therapeutic-alternative-element
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package; no repo URL typical for private/internal components. | ai | |
| phantom-deps | phantom-dep:tctx | AI (phantom-deps): Build/config-only reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lit/localize | AI (phantom-deps): Build/config-only reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lit-labs/signals | AI (phantom-deps): Build/config-only reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:vite-tsconfig-paths | AI (phantom-deps): Build/config-only reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@hey-api/client-fetch | AI (phantom-deps): Build/config-only reference; stable pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.6 | 6 / 35 | |
| 1.0.5 | 6 / 35 | |
| 1.0.4 | 6 / 35 | |
| 1.0.3 | 6 / 35 | |
| 1.0.2 | 6 / 35 | |
| 1.0.1 | 6 / 35 | |
| 1.0.0 | 6 / 35 | |
| 0.1.0 | 6 / 35 |
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.