@holochain-open-dev/core-types
Typescript types for holochain core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@holochain/client | AI (dependencies): Expected core dependency for a Holochain types package; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Holochain ecosystem package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.601.2 | 1 / 4 | |
| 0.601.0 | 1 / 5 | |
| 0.600.0 | 1 / 10 | |
| 0.500.0 | 1 / 10 | |
| 0.400.0 | 1 / 10 | |
| 0.300.0 | 1 / 4 | |
| 0.7.0 | 1 / 10 | |
| 0.6.6 | 1 / 9 | |
| 0.6.4 | 1 / 9 | |
| 0.6.3 | 1 / 9 | |
| 0.6.2 | 2 / 9 | |
| 0.6.1 | 2 / 9 | |
| 0.6.0 | 2 / 9 | |
| 0.5.0 | 2 / 9 | |
| 0.4.1 | 2 / 9 | |
| 0.4.0 | 2 / 9 | |
| 0.3.1 | 2 / 9 | |
| 0.3.0 | 2 / 9 | |
| 0.2.1 | 2 / 9 | |
| 0.2.0 | 2 / 9 |
v0.400.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.
v0.300.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.
v0.7.0
2 findings[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 (matthme) than the most recent previously approved version (zippy314) on 2023-08-10, but matthme 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.6.6
2 findings[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 (guillem.cordoba) than the most recent previously approved version (zippy314) on 2023-02-16, but guillem.cordoba 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.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findings[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 (guillem.cordoba) than the most recent previously approved version (zippy314) on 2023-01-02, but guillem.cordoba 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.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findings[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 (zippy314) than the most recent previously approved version (matthme) on 2022-12-07, but zippy314 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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
2 findingsThis version was published by a different npm account (matthme) than the most recent previously approved version (guillem.cordoba) on 2022-08-21. It has since remained available on npm for 1434 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.