← Home

@prismicio/client

npm Repository Homepage
45
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

chrrrssamuelhornprismicsrearnaudlewismichel.chaugholgotodimprismic-cilihbrbapmrlangeloashmorelevimykelnvldboubiyeahfilipeueruben-prismicpaulyvpgjomifepexrutayisiretomabororelisuiari-prismicgreenwalker90

Keywords

clientcmshelpersprismicprismic.iotoolboxtypestypescriptutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Well-known unified/remark/rehype ecosystem deps supporting richtext feature, not suspicious. ai
source-diff large-new-source-files AI (source-diff): Growth corresponds to legitimate new richtext feature, not injected code. ai
provenance publisher-changed AI (provenance): dani-mp is a known Prismic org maintainer with 11 approved packages; transition appears legitimate. ai

Versions (showing 45 of 45)

Version Deps Published
7.21.8 1 / 9
7.21.7 1 / 11
7.21.6 1 / 11
7.21.5 1 / 11
7.21.4 1 / 11
7.21.3 1 / 11
7.21.2 1 / 11
7.21.1 1 / 11
7.21.0 1 / 23
7.20.3 1 / 23
7.20.2 1 / 23
7.20.1 1 / 23
7.20.0 1 / 23
7.19.2 1 / 23
7.19.1 1 / 23
7.19.0 1 / 23
7.18.3 1 / 23
7.18.2 1 / 23
7.18.1 1 / 23
7.18.0 1 / 23
7.17.3 1 / 23
7.17.2 1 / 23
7.17.1 1 / 23
7.17.0 1 / 23
7.16.1 1 / 23
7.16.0 1 / 23
7.15.1 1 / 23
7.15.0 1 / 23
7.14.0 1 / 23
7.13.1 1 / 23
7.13.0 1 / 23
7.12.0 1 / 23
7.11.1 1 / 23
7.11.0 1 / 23
7.10.1 1 / 23
7.10.0 1 / 23
7.9.0 1 / 23
7.8.1 1 / 23
7.8.0 1 / 23
7.7.4 13 / 23
7.7.3 13 / 23
7.7.2 13 / 23
7.7.1 13 / 23
7.7.0 13 / 23
7.6.0 1 / 23

v7.17.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → angeloashmore (on 2025-04-10, known maintainer) provenance

This version was published by a different npm account (angeloashmore) than the most recent previously approved version (xrutayisire) on 2025-04-10, but angeloashmore 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.

v7.17.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2025-03-31, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2025-03-31, but lihbr 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.

v7.17.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dani-mp → xrutayisire (on 2025-03-19, known maintainer) provenance

This version was published by a different npm account (xrutayisire) than the most recent previously approved version (dani-mp) on 2025-03-19, but xrutayisire 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.

v7.16.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dani-mp → levimykel (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (levimykel) than the most recent previously approved version (dani-mp) on 2025-02-20, but levimykel 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.

v7.16.0

1 finding
LOW No provenance attestation provenance

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

v7.15.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dani-mp → lihbr (on 2025-01-16, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (dani-mp) on 2025-01-16, but lihbr 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.

v7.15.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → dani-mp (on 2025-01-15, known maintainer) provenance

This version was published by a different npm account (dani-mp) than the most recent previously approved version (xrutayisire) on 2025-01-15, but dani-mp 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.

v7.14.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → dani-mp (on 2025-01-09, known maintainer) provenance

This version was published by a different npm account (dani-mp) than the most recent previously approved version (xrutayisire) on 2025-01-09, but dani-mp 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.

v7.13.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: angeloashmore → xrutayisire (on 2024-12-11, known maintainer) provenance

This version was published by a different npm account (xrutayisire) than the most recent previously approved version (angeloashmore) on 2024-12-11, but xrutayisire 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.

v7.13.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: angeloashmore → dani-mp (on 2024-12-05, known maintainer) provenance

This version was published by a different npm account (dani-mp) than the most recent previously approved version (angeloashmore) on 2024-12-05, but dani-mp 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.

v7.12.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dani-mp → angeloashmore (on 2024-10-30, known maintainer) provenance

This version was published by a different npm account (angeloashmore) than the most recent previously approved version (dani-mp) on 2024-10-30, but angeloashmore 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.

v7.11.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dani-mp → lihbr (on 2024-10-30, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (dani-mp) on 2024-10-30, but lihbr 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.

v7.11.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: lihbr → dani-mp (on 2024-09-25, known maintainer) provenance

This version was published by a different npm account (dani-mp) than the most recent previously approved version (lihbr) on 2024-09-25, but dani-mp 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.

v7.10.1

1 finding
LOW No provenance attestation provenance

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

v7.10.0

1 finding
LOW No provenance attestation provenance

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

v7.9.0

1 finding
LOW No provenance attestation provenance

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

v7.8.1

1 finding
LOW No provenance attestation provenance

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

v7.8.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-08-01, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-08-01, but lihbr 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.

v7.7.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-07-24, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-07-24, but lihbr 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.

v7.7.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-07-23, but lihbr 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.

v7.7.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-07-23, but lihbr 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.

v7.7.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-07-23, but lihbr 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.

v7.7.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: xrutayisire → lihbr (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (lihbr) than the most recent previously approved version (xrutayisire) on 2024-07-23, but lihbr 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.

v7.6.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.