← Home

@npmcli/name-from-folder

npm Repository Homepage

Get the package name from a folder path

6
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

saquibkhannpm-cli-opsreggiowlstronaut

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from isaacs to lukekarrys reflects a known npm org team transition; lukekarrys is a well-established npm CLI team member. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (saquibkhan, fritzy, nlf, gar, lukekarrys) are all known npm/GitHub org members; reflects org-level team restructuring, not a takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers (ruyadorno, claudiahdz, adam_baldwin, isaacs) are consistent with the same npm org team transition; not indicative of compromise. ai

Versions (showing 6 of 6)

Version Deps Published
5.0.0 0 / 2
4.0.0 0 / 3
3.0.0 0 / 3
2.0.0 0 / 3
1.0.1 0 / 1
1.0.0 0 / 1

v5.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.0

2 findings
HIGH Publisher changed: isaacs → lukekarrys (on 2022-12-13) provenance

This version was published by a different npm account than previous versions on 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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