@hashgraph/proto No license 26 versions

@hashgraph/proto

npm Repository Homepage

26

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

steven.sheehymehcodeswirldslabs-admindanielakhterovpetrezedaniel.k.ivanovgeorgi-l95ochikovrbair23michielmuldersnathan-swirldslabsstoqnkpisavovhedera-eng-automationnana-ec

Keywords

hierohederahashgraphsdktransactions

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Long-stable publisher transition from years ago, not a fresh takeover signal.	ai	2026/07/21
provenance	publisher-changed-stale	AI (provenance): Stale change, unremoved for 1280 days; consistent with legitimate org transfer.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Mature, high-download SDK package; dormancy reflects release cadence, not takeover.	ai	2026/07/21
publish-pattern	new-deps-added	AI (publish-pattern): Added dep is `long`, a trivial well-known utility library.	ai	2026/07/21

Versions (showing 26 of 26)

Version	Deps	Published
2.25.0	1 / 29	2025-11-20
2.24.0	1 / 29	2025-10-16
2.15.0	2 / 28	2024-06-06
2.13.0	2 / 28	2023-07-17
2.12.0	3 / 27	2023-02-14
2.11.2	2 / 27	2023-01-18
2.11.1	2 / 27	2023-01-05
2.11.0	2 / 27	2022-10-04
2.10.0	2 / 27	2022-09-19
2.9.0	2 / 28	2022-08-01
2.8.0	2 / 26	2022-07-19
2.7.0	2 / 26	2022-07-06
2.6.0	2 / 26	2022-06-21
2.5.0	2 / 26	2022-06-01
2.4.2	2 / 26	2022-04-30
2.4.1	2 / 26	2022-04-27
2.4.0	2 / 26	2022-04-18
2.3.0	2 / 26	2022-04-05
2.2.0	2 / 26	2022-03-21
2.1.5	2 / 25	2022-02-27
2.1.4	2 / 25	2022-02-15
2.1.3	1 / 25	2022-01-31
2.1.2	1 / 18	2022-01-15
2.1.1	1 / 18	2021-12-17
2.1.0	1 / 18	2021-12-14
2.0.0	1 / 18	2021-09-01

v2.15.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.

v2.13.0

2 findings

MEDIUM Publisher changed: danielakhterov → petreze (on 2023-07-17, unremoved on npm for 1100d) provenance

This version was published by a different npm account (petreze) than the most recent previously approved version (danielakhterov) on 2023-07-17. It has since remained available on npm for 1100 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.12.0

2 findings

MEDIUM Publisher changed: danielakhterov → ochikov (on 2023-02-14, unremoved on npm for 1253d) provenance

This version was published by a different npm account (ochikov) than the most recent previously approved version (danielakhterov) on 2023-02-14. It has since remained available on npm for 1253 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.11.2

2 findings

MEDIUM Publisher changed: danielakhterov → ochikov (on 2023-01-18, unremoved on npm for 1280d) provenance

This version was published by a different npm account (ochikov) than the most recent previously approved version (danielakhterov) on 2023-01-18. It has since remained available on npm for 1280 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.11.1

2 findings

MEDIUM Publisher changed: danielakhterov → ochikov (on 2023-01-05, unremoved on npm for 1293d) provenance

This version was published by a different npm account (ochikov) than the most recent previously approved version (danielakhterov) on 2023-01-05. It has since remained available on npm for 1293 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.0

1 finding

LOW No provenance attestation provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.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.

v2.0.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.