@datagrok/tutorials
Learn and explore Datagrok through interactive tutorials and a demo app
Supply chain provenance
Status for the latest visible version.
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
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): Monorepo plugin; library referenced in config/webpack but not directly imported in source is expected. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.11.2 | 8 / 12 | |
| 1.11.1 | 8 / 12 | |
| 1.11.0 | 8 / 12 | |
| 1.10.6 | 7 / 12 | |
| 1.10.5 | 7 / 12 |
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.