@operato/data-grist — Greenflagged

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

heartyohchayeongronggayeon4041jay_leewoo_ramnalshya113

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@operato/p13n	AI (dependencies): Same-monorepo sibling dep; stable pattern across all @operato/data-grist versions.	ai	2026/05/18
dependencies	unvetted-dep:@operato/input	AI (dependencies): Same-monorepo sibling dep; stable pattern across all @operato/data-grist versions.	ai	2026/05/18
dependencies	unvetted-dep:@operato/headroom	AI (dependencies): Same-monorepo sibling dep; stable pattern across all @operato/data-grist versions.	ai	2026/05/18
dependencies	unvetted-dep:@operato/pull-to-refresh	AI (dependencies): Same-monorepo sibling dep; stable pattern across all @operato/data-grist versions.	ai	2026/05/18
dependencies	unvetted-dep:@operato/time-calculator	AI (dependencies): Same-monorepo sibling dep; stable pattern across all @operato/data-grist versions.	ai	2026/05/18
provenance	no-provenance	AI (provenance): Established package with 762 versions; provenance not historically used by this package.	ai	2026/05/06

Versions (showing 27 of 27)

Version	Deps	Published
9.2.25	13 / 18	2026-05-27
9.2.22	13 / 18	2026-05-12
9.2.21	13 / 18	2026-05-07
9.2.20	13 / 18	2026-05-06
9.2.19	13 / 18	2026-05-04
9.2.18	13 / 18	2026-04-24
9.2.16	13 / 18	2026-04-14
9.2.15	13 / 18	2026-04-09
9.2.14	13 / 18	2026-04-07
9.2.13	13 / 18	2026-04-01
9.2.12	13 / 18	2026-03-19
9.2.7	13 / 18	2026-03-12
9.2.6	13 / 18	2026-03-09
9.2.5	13 / 18	2026-03-06
9.2.1	13 / 18	2025-11-09
9.2.0	13 / 18	2025-11-09
8.2.24	13 / 18	2026-04-14
8.2.23	13 / 18	2026-04-14
8.2.22	13 / 18	2026-04-10
8.2.20	13 / 18	2026-02-09
8.2.19	13 / 18	2026-01-09
8.2.18	13 / 18	2025-12-24
8.2.17	13 / 18	2025-12-04
8.2.16	13 / 18	2025-11-30
8.2.15	13 / 18	2025-11-28
8.2.14	13 / 18	2025-11-28
8.2.13	13 / 18	2025-11-10

v9.2.25

1 finding

INFO No provenance attestation provenance

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

v9.2.22

1 finding

INFO No provenance attestation provenance

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

v9.2.21

1 finding

INFO No provenance attestation provenance

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

v9.2.20

1 finding

INFO No provenance attestation provenance

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

v9.2.19

1 finding

INFO No provenance attestation provenance

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

v9.2.18

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.

v9.2.16

1 finding

INFO No provenance attestation provenance

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

v9.2.15

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.

v9.2.14

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.

v9.2.13

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.

v9.2.12

1 finding

INFO No provenance attestation provenance

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

v9.2.7

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.

v9.2.6

1 finding

INFO No provenance attestation provenance

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

v9.2.5

1 finding

INFO No provenance attestation provenance

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

v9.2.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.

v9.2.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.

v8.2.24

1 finding

INFO No provenance attestation provenance

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

v8.2.23

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.

v8.2.22

1 finding

INFO No provenance attestation provenance

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

v8.2.20

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.

v8.2.19

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.

v8.2.18

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.

v8.2.17

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.

v8.2.16

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.

v8.2.15

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.

v8.2.14

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.

v8.2.13

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-11-10, known maintainer) provenance

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