@holochain-open-dev/profiles
Frontend module for the Holochain hc_zome_profiles zomes
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lit | AI (phantom-deps): Web component library; lit is re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@lit/context | AI (phantom-deps): Web component library; re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@lit/localize | AI (phantom-deps): Web component library; re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@mdi/js | AI (phantom-deps): Web component library; re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@shoelace-style/shoelace | AI (phantom-deps): Web component library; re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@holochain/client | AI (phantom-deps): Holochain library; re-exported via stores dependency. | ai | |
| phantom-deps | phantom-dep:@holochain-open-dev/utils | AI (phantom-deps): Same-org dependency; re-exported via stores dependency. | ai | |
| phantom-deps | phantom-dep:@holochain-open-dev/stores | AI (phantom-deps): Same-org dependency; re-exported via elements dependency. | ai | |
| phantom-deps | phantom-dep:@holochain-open-dev/elements | AI (phantom-deps): Same-org dependency; re-exported as primary export. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.601.4 | 9 / 16 | |
| 0.601.3 | 9 / 16 | |
| 0.601.0 | 9 / 16 | |
| 0.600.0 | 9 / 16 | |
| 0.501.2 | 9 / 16 | |
| 0.501.0 | 9 / 16 |
v0.601.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.601.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.601.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.600.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.501.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.501.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.