← Home

@ehmpathy/as-command

npm Repository Homepage
3
Versions
—
License
Yes
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

uladkasach

Keywords

timedatedatetimeUniDateUniDateTimeUniDuration

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Standard husky dev-hooks setup; no-op outside a git repo, safe for end-users. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.5 2 / 25
1.0.4 2 / 25
1.0.3 2 / 24

v1.0.5

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npx husky install || exit 0

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.

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: [ -d .git ] && npx husky install || exit 0

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.