← Home

@operato/dataset

npm Repository
8
Versions
—
License
No
Install Scripts
Missing
Provenance

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.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established @operato org package; no provenance is consistent across all versions in this ecosystem. ai
phantom-deps phantom-dep:@operato/shell AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on indirect/re-exported usage patterns. ai
phantom-deps phantom-dep:@operato/graphql AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@operato/grist-editor AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
9.2.25 12 / 17
9.2.12 12 / 17
9.2.7 12 / 17
9.2.4 12 / 17
9.2.3 12 / 17
9.2.2 12 / 17
9.2.1 12 / 17
9.2.0 12 / 17

v9.2.25

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 2026-05-27, known maintainer) provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v9.2.4

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.3

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

1 finding
LOW No provenance attestation provenance

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. Consider requesting the maintainer enable provenance via CI/CD.

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.