← Home

posix-getopt

POSIX-style getopt()

5
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

trentmdapjclulowbahamat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from dap to bahamat/trentm/jclulow reflects a legitimate Joyent team handoff; all new maintainers are well-known Node.js ecosystem contributors with clean track records. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (trentm, jclulow, bahamat) are established Joyent engineers; this is a legitimate team transition, not a hostile takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy is consistent with a stable, feature-complete utility; the eventual publish coincides with a known team transition, not suspicious activity. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.1 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.0 0 / 0
0.0.1 0 / 0

v1.2.1

2 findings
HIGH Publisher changed: dap → bahamat (on 2021-11-03) provenance

This version was published by a different npm account than previous versions on 2021-11-03. 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.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

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.