isotopic-distribution
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
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.8.1 | 5 / 1 | |
| 3.8.0 | 5 / 1 | |
| 3.7.0 | 5 / 1 | |
| 3.6.0 | 5 / 1 | |
| 3.5.0 | 5 / 1 | |
| 3.4.18 | 5 / 1 | |
| 3.4.17 | 5 / 1 | |
| 3.4.16 | 5 / 1 | |
| 3.4.15 | 5 / 1 | |
| 3.4.14 | 5 / 1 | |
| 3.4.13 | 5 / 1 | |
| 3.4.12 | 5 / 1 | |
| 3.4.11 | 5 / 1 | |
| 3.4.10 | 5 / 1 | |
| 3.4.9 | 5 / 1 | |
| 3.4.8 | 5 / 1 | |
| 3.4.7 | 5 / 1 | |
| 3.4.6 | 5 / 1 | |
| 3.4.5 | 4 / 1 | |
| 3.4.4 | 4 / 1 | |
| 3.4.3 | 4 / 1 | |
| 3.4.2 | 4 / 1 | |
| 3.4.1 | 4 / 1 | |
| 3.4.0 | 4 / 1 | |
| 3.3.3 | 4 / 1 | |
| 3.3.2 | 4 / 1 | |
| 3.3.1 | 4 / 1 | |
| 3.3.0 | 4 / 1 | |
| 3.2.2 | 4 / 1 | |
| 3.2.1 | 4 / 1 | |
| 3.2.0 | 4 / 1 |
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cheminfo-bot) than the most recent previously approved version (targos) on 2024-08-06, but cheminfo-bot 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.
v3.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (cheminfo-bot) than the most recent previously approved version (targos) on 2024-08-02, but cheminfo-bot 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.
v3.2.2
2 findingsThis version was published by a different npm account (targos) than the most recent previously approved version (cheminfo-bot) on 2024-07-31. It has since remained available on npm for 717 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsThis version was published by a different npm account (targos) than the most recent previously approved version (cheminfo-bot) on 2024-07-08. It has since remained available on npm for 740 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.