@datagrok-libraries/tutorials No license 8 versions

@datagrok-libraries/tutorials

npm

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

aparamonov_datagrokspodgrok

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@datagrok-libraries/utils	AI (phantom-deps): Same org scope; phantom-dep false positive for monorepo-style packages.	ai	2026/04/30
phantom-deps	phantom-dep:dayjs	AI (phantom-deps): Pinned version in dependencies; likely used transitively or in config — stable false positive for this package.	ai	2026/04/30

Versions (showing 8 of 8)

Version	Deps	Published
1.7.7	6 / 9	2026-05-16
1.7.6	6 / 9	2026-03-23
1.7.5	6 / 9	2026-03-06
1.7.4	6 / 9	2025-10-07
1.7.3	6 / 9	2025-09-17
1.7.2	6 / 9	2025-09-12
1.7.1	6 / 9	2025-09-12
1.7.0	6 / 9	2025-07-25

v1.7.7

1 finding

LOW No provenance attestation provenance

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

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

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

v1.7.4

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.

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

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

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

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