← Home

parse-semver

npm Repository Homepage

Parse, normalize and validate given semver shorthand (e.g. [email protected]) to object.

4
Versions
MIT
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

tunnckocore

Keywords

equalhelperiskindofnormalizenpmobjectparseparserrangesemvershallowshortshorthandutilsvalidateversion

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:tunnckocore AI (email-domain): Long-standing legitimate package/publisher; domain quirk, not a takeover indicator here. ai
provenance no-provenance AI (provenance): Established package predating Sigstore provenance; absence is expected and stable. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.1 1 / 1
1.1.0 1 / 1
1.0.1 1 / 3
1.0.0 1 / 3

v1.1.0

2 findings
HIGH Unclaimed maintainer email domain: tunnckocore email-domain

Maintainer email '@tunnckoCore' uses domain 'tunnckocore' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v1.0.1

1 finding
INFO No provenance attestation provenance

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

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.