@zakodium/nmrium-core
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:@zakodium/utils | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via bundling — stable false positive for this package. | ai | |
| dependencies | unvetted-dep:nmr-correlation | AI (dependencies): nmr-correlation is a domain-specific NMR library from the same Zakodium ecosystem; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; no provenance attestation but no other risk signals; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:is-any-array | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ml-spectra-processing | AI (phantom-deps): Config-file reference only; stable false positive for this package. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 0.7.50 | 8 / 18 | |
| 0.7.49 | 8 / 18 | |
| 0.7.48 | 8 / 18 | |
| 0.7.47 | 8 / 18 | |
| 0.7.46 | 8 / 18 | |
| 0.7.45 | 8 / 18 | |
| 0.7.44 | 8 / 18 | |
| 0.7.43 | 8 / 18 | |
| 0.7.42 | 8 / 18 | |
| 0.7.41 | 8 / 18 | |
| 0.7.40 | 8 / 18 | |
| 0.7.39 | 8 / 18 | |
| 0.7.38 | 8 / 18 | |
| 0.7.37 | 8 / 18 | |
| 0.7.36 | 8 / 18 | |
| 0.7.35 | 8 / 18 | |
| 0.7.34 | 7 / 18 | |
| 0.7.33 | 7 / 18 | |
| 0.7.32 | 7 / 18 | |
| 0.7.31 | 7 / 18 | |
| 0.7.30 | 7 / 18 | |
| 0.7.29 | 7 / 18 | |
| 0.7.28 | 7 / 18 | |
| 0.7.27 | 7 / 18 | |
| 0.7.26 | 7 / 18 | |
| 0.7.25 | 7 / 18 | |
| 0.7.24 | 7 / 18 | |
| 0.7.23 | 7 / 16 | |
| 0.7.22 | 7 / 16 | |
| 0.7.21 | 7 / 16 | |
| 0.7.20 | 7 / 16 | |
| 0.7.19 | 7 / 16 | |
| 0.7.18 | 7 / 16 | |
| 0.7.17 | 7 / 16 | |
| 0.7.16 | 7 / 16 | |
| 0.7.15 | 7 / 16 | |
| 0.7.14 | 7 / 16 | |
| 0.7.13 | 7 / 16 | |
| 0.7.12 | 7 / 16 | |
| 0.7.11 | 7 / 16 | |
| 0.7.10 | 7 / 16 | |
| 0.7.9 | 7 / 16 | |
| 0.7.8 | 7 / 16 | |
| 0.7.7 | 7 / 11 | |
| 0.7.6 | 7 / 11 | |
| 0.7.5 | 7 / 11 | |
| 0.7.4 | 7 / 11 | |
| 0.7.3 | 7 / 11 | |
| 0.7.2 | 7 / 11 | |
| 0.7.1 | 7 / 11 | |
| 0.7.0 | 7 / 11 | |
| 0.6.8 | 7 / 11 | |
| 0.6.7 | 7 / 11 | |
| 0.6.6 | 7 / 11 | |
| 0.6.5 | 7 / 11 | |
| 0.6.4 | 7 / 11 | |
| 0.6.3 | 7 / 11 | |
| 0.6.2 | 7 / 10 | |
| 0.6.1 | 7 / 9 | |
| 0.6.0 | 7 / 9 | |
| 0.5.8 | 7 / 9 | |
| 0.5.7 | 7 / 9 | |
| 0.5.6 | 7 / 9 | |
| 0.5.5 | 7 / 9 | |
| 0.5.4 | 7 / 9 | |
| 0.5.3 | 7 / 9 | |
| 0.5.2 | 7 / 9 | |
| 0.5.1 | 7 / 9 | |
| 0.5.0 | 7 / 9 | |
| 0.4.13 | 7 / 9 | |
| 0.4.12 | 7 / 9 | |
| 0.4.11 | 7 / 9 | |
| 0.4.10 | 7 / 9 | |
| 0.4.9 | 7 / 9 | |
| 0.4.8 | 7 / 9 | |
| 0.4.7 | 7 / 9 | |
| 0.4.6 | 7 / 9 | |
| 0.4.5 | 7 / 9 | |
| 0.4.4 | 7 / 9 | |
| 0.4.3 | 7 / 9 | |
| 0.4.2 | 7 / 9 | |
| 0.4.1 | 7 / 9 | |
| 0.4.0 | 7 / 9 | |
| 0.3.0 | 7 / 9 | |
| 0.2.3 | 7 / 9 | |
| 0.2.2 | 7 / 8 | |
| 0.2.1 | 7 / 8 | |
| 0.2.0 | 7 / 8 | |
| 0.1.7 | 7 / 8 | |
| 0.1.6 | 7 / 8 | |
| 0.1.5 | 7 / 8 | |
| 0.1.4 | 7 / 7 | |
| 0.1.3 | 7 / 7 | |
| 0.1.2 | 8 / 6 | |
| 0.1.1 | 8 / 7 | |
| 0.1.0 | 8 / 12 | |
| 0.0.2 | 8 / 12 | |
| 0.0.1 | 8 / 12 |
v0.7.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.