@autifyhq/autify-cli
Autify Command Line Interface (CLI)
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 26 of 26)
| 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 | |
| 0.58.0 | 22 / 30 | |
| 0.56.0 | 22 / 30 | |
| 0.54.0 | 22 / 30 | |
| 0.53.0 | 22 / 27 | |
| 0.52.0 | 22 / 27 | |
| 0.51.0 | 23 / 28 | |
| 0.50.0 | 23 / 26 | |
| 0.49.0 | 23 / 27 | |
| 0.48.0 | 23 / 27 | |
| 0.47.0 | 23 / 27 | |
| 0.46.0 | 24 / 28 | |
| 0.45.0 | 24 / 29 |
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.