@datagrok-libraries/tutorials No license 22 versions

@datagrok-libraries/tutorials

npm

22

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

aparamonov_datagrokdrizhinaspodgrok

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:src/demo-base-view.js	AI (source-diff): TS-compiled output with tslib helpers, not true obfuscation; legitimate UI code.	ai	2026/07/16
bogus-package	bogus-package	AI (bogus-package): Internal library sibling package from trusted Datagrok org, thin README is normal.	ai	2026/07/16
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 22 of 22)

Version	Deps	Published
1.7.8	6 / 9	2026-07-12
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
1.6.2	6 / 8	2025-04-02
1.6.1	6 / 8	2025-04-01
1.6.0	6 / 8	2025-03-29
1.5.4	6 / 8	2025-02-11
1.5.3	6 / 8	2024-12-27
1.5.2	6 / 8	2024-11-29
1.5.1	6 / 8	2024-11-22
1.5.0	4 / 7	2024-11-12
1.4.3	4 / 7	2024-10-03
1.4.2	4 / 7	2024-10-02
1.4.1	4 / 7	2024-09-13
1.4.0	4 / 7	2024-09-09
1.3.13	4 / 7	2024-08-07

v1.7.8

1 finding

LOW No provenance attestation provenance

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

v1.6.2

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.6.1

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.6.0

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.4

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.3

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.2

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.1

2 findings

HIGH New obfuscated file: src/demo-base-view.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

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