@fireproof/core-types-protocols-cloud No license 21 versions

@fireproof/core-types-protocols-cloud

npm Repository Homepage

21

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jchrisfastandfearless

Keywords

ledgerJSONdocumentIPLDCIDIPFS

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:jose	AI (phantom-deps): jose is a declared runtime dep used by cloud protocol types; phantom-dep heuristic false positive for type-only packages.	ai	2026/05/23
phantom-deps	phantom-dep:multiformats	AI (phantom-deps): multiformats is a declared dep in this IPLD-based package; phantom-dep heuristic false positive.	ai	2026/05/23
phantom-deps	phantom-dep:@fireproof/vendor	AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic not meaningful here.	ai	2026/05/23

Versions (showing 21 of 21)

Version	Deps	Published
0.24.19	7 / 0	2026-04-15
0.24.16	7 / 0	2026-03-28
0.24.15	7 / 0	2026-03-27
0.24.14	7 / 0	2026-03-27
0.24.13	7 / 0	2026-03-16
0.24.12	7 / 0	2026-02-20
0.24.11	7 / 0	2026-02-12
0.24.0	7 / 0	2025-11-30
0.23.15	7 / 1	2025-10-16
0.23.14	7 / 1	2025-10-02
0.23.13	6 / 1	2025-08-27
0.23.11	6 / 1	2025-08-23
0.23.10	6 / 1	2025-08-23
0.23.8	6 / 1	2025-08-23
0.23.7	6 / 1	2025-08-23
0.23.6	6 / 1	2025-08-19
0.23.5	6 / 1	2025-08-19
0.23.3	6 / 1	2025-08-19
0.23.2	6 / 1	2025-08-15
0.23.1	6 / 1	2025-08-13
0.23.0	6 / 1	2025-08-09

v0.24.16

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.15

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.14

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.13

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.12

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.11

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.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.

v0.23.15

1 finding

LOW No provenance attestation provenance

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

v0.23.14

1 finding

LOW No provenance attestation provenance

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

v0.23.13

1 finding

LOW No provenance attestation provenance

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

v0.23.11

1 finding

LOW No provenance attestation provenance

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

v0.23.10

1 finding

LOW No provenance attestation provenance

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

v0.23.8

1 finding

LOW No provenance attestation provenance

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

v0.23.7

1 finding

LOW No provenance attestation provenance

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

v0.23.6

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.

v0.23.5

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.

v0.23.3

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.

v0.23.2

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.

v0.23.1

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.

v0.23.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.