mf-parser
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 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.9.2 | 3 / 1 | |
| 3.9.1 | 3 / 1 | |
| 3.9.0 | 3 / 1 | |
| 3.8.0 | 3 / 1 | |
| 3.7.2 | 3 / 1 | |
| 3.7.1 | 3 / 1 | |
| 3.7.0 | 3 / 1 | |
| 3.6.0 | 3 / 1 | |
| 3.5.0 | 3 / 1 | |
| 3.4.2 | 3 / 1 | |
| 3.4.1 | 3 / 1 | |
| 3.4.0 | 3 / 1 | |
| 3.3.1 | 3 / 1 | |
| 3.3.0 | 3 / 1 | |
| 3.2.8 | 3 / 1 | |
| 3.2.7 | 3 / 1 | |
| 3.2.6 | 3 / 1 | |
| 3.2.5 | 3 / 1 | |
| 3.2.4 | 3 / 1 | |
| 3.2.3 | 3 / 1 | |
| 3.2.2 | 3 / 1 | |
| 3.2.1 | 3 / 1 | |
| 3.2.0 | 4 / 1 |
v3.9.2
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
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.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.