← Home

@autifyhq/autify-cli

npm Repository Homepage

Autify Command Line Interface (CLI)

14
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

syamashitaautifyhq-releasefadhlirahimkristine.tanthomas.santonjajsravencroft

Keywords

oclif

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from autifyhq-release to GitHub Actions is a documented CI/CD migration; SLSA attestation confirms legitimate pipeline. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by GitHub Actions publish with SLSA provenance is consistent with a CI pipeline migration, not account takeover. ai
phantom-deps phantom-dep:@oclif/plugin-not-found AI (phantom-deps): oclif plugins are loaded via config, not direct imports; stable false positive for oclif CLIs. ai
phantom-deps phantom-dep:@oclif/plugin-help AI (phantom-deps): oclif plugins are loaded via config, not direct imports; stable false positive for oclif CLIs. ai
phantom-deps phantom-dep:per-env AI (phantom-deps): per-env is used in prepare script via CLI invocation, not a direct import; stable false positive. ai
phantom-deps phantom-dep:@oclif/plugin-warn-if-update-available AI (phantom-deps): oclif plugins are loaded via config, not direct imports; stable false positive for oclif CLIs. ai
phantom-deps phantom-dep:@oclif/plugin-update AI (phantom-deps): oclif plugins are loaded via config, not direct imports; stable false positive for oclif CLIs. ai

Versions (showing 14 of 14)

Version Deps Published
0.73.2 25 / 28
0.73.1 25 / 28
0.73.0 25 / 28
0.72.0 25 / 30
0.70.0 24 / 30
0.69.0 24 / 30
0.68.0 24 / 30
0.67.0 24 / 30
0.66.0 22 / 30
0.65.0 22 / 30
0.63.0 22 / 30
0.62.0 22 / 30
0.61.0 22 / 30
0.60.0 22 / 30

v0.73.2

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.

v0.73.1

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.

v0.73.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.

v0.72.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.

v0.69.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.

v0.68.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.

v0.67.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.

v0.66.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.

v0.65.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.

v0.63.0

2 findings
HIGH Publisher changed: autifyhq-release → GitHub Actions (on 2025-10-21) provenance

This version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.

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.

v0.62.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.

v0.61.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.

v0.60.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.