@autifyhq/autify-cli-integration-test
Autify Command Line Interface (CLI) Integration Test
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pollyjs/adapter-node-http | AI (dependencies): Part of the @pollyjs suite; stable dependency for this integration test package. | ai | |
| dependencies | unvetted-dep:@pollyjs/core | AI (dependencies): Well-known Netflix OSS HTTP mocking library; stable dependency for this integration test package. | ai | |
| dependencies | unvetted-dep:@pollyjs/persister | AI (dependencies): Part of the @pollyjs suite; stable dependency for this integration test package. | ai | |
| dependencies | unvetted-dep:@pollyjs/persister-fs | AI (dependencies): Part of the @pollyjs suite; stable dependency for this integration test package. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): jest is referenced in test scripts/config, not imported directly; stable false positive for this test package. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): cross-env is used in npm scripts, not imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): strip-ansi used in test utilities/config, not directly imported; stable false positive. | ai | |
| phantom-deps | phantom-dep:@pollyjs/persister | AI (phantom-deps): @pollyjs/persister is a base class dependency used indirectly; stable false positive for this package. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.73.3 | 11 / 7 | |
| 0.73.2 | 11 / 7 | |
| 0.73.1 | 11 / 7 | |
| 0.73.0 | 11 / 7 | |
| 0.72.0 | 11 / 7 | |
| 0.70.0 | 11 / 7 | |
| 0.69.0 | 11 / 7 | |
| 0.68.0 | 11 / 7 | |
| 0.67.0 | 11 / 7 | |
| 0.66.0 | 11 / 7 | |
| 0.63.0 | 11 / 7 | |
| 0.62.0 | 11 / 7 | |
| 0.61.0 | 11 / 7 | |
| 0.60.0 | 11 / 7 | |
| 0.58.0 | 11 / 7 | |
| 0.56.0 | 11 / 7 | |
| 0.54.0 | 11 / 7 | |
| 0.53.0 | 11 / 7 | |
| 0.52.0 | 11 / 7 | |
| 0.51.0 | 11 / 7 | |
| 0.50.0 | 11 / 7 | |
| 0.49.0 | 11 / 7 | |
| 0.48.0 | 11 / 7 | |
| 0.47.0 | 11 / 7 | |
| 0.46.0 | 11 / 7 | |
| 0.45.0 | 11 / 7 | |
| 0.44.0 | 11 / 7 | |
| 0.43.0 | 11 / 7 | |
| 0.42.0 | 11 / 7 | |
| 0.41.0 | 11 / 7 | |
| 0.40.0 | 11 / 7 | |
| 0.39.0 | 11 / 7 | |
| 0.38.0 | 11 / 7 | |
| 0.37.0 | 11 / 7 | |
| 0.36.0 | 11 / 7 | |
| 0.35.0 | 11 / 7 | |
| 0.34.0 | 11 / 7 | |
| 0.33.0 | 11 / 7 | |
| 0.32.0 | 11 / 7 | |
| 0.31.0 | 11 / 7 | |
| 0.30.0 | 11 / 7 | |
| 0.29.0 | 11 / 7 | |
| 0.28.0 | 11 / 7 | |
| 0.27.0 | 11 / 7 | |
| 0.26.0 | 11 / 7 | |
| 0.24.0 | 11 / 7 | |
| 0.23.0 | 11 / 7 | |
| 0.22.0 | 11 / 7 | |
| 0.21.0 | 11 / 7 | |
| 0.20.0 | 11 / 7 | |
| 0.19.0 | 11 / 7 | |
| 0.18.0 | 11 / 7 | |
| 0.17.0 | 11 / 7 | |
| 0.16.0 | 11 / 7 | |
| 0.15.0 | 11 / 7 | |
| 0.14.0 | 11 / 7 | |
| 0.13.0 | 11 / 7 | |
| 0.12.0 | 11 / 7 | |
| 0.11.0 | 11 / 7 | |
| 0.10.1 | 11 / 7 | |
| 0.10.0 | 11 / 7 | |
| 0.9.0 | 10 / 7 | |
| 0.8.0 | 10 / 7 | |
| 0.7.2 | 10 / 7 | |
| 0.7.1 | 10 / 7 | |
| 0.7.0 | 10 / 7 | |
| 0.6.1 | 10 / 7 | |
| 0.6.0 | 10 / 7 | |
| 0.5.0 | 8 / 7 | |
| 0.4.0 | 8 / 7 | |
| 0.3.1 | 8 / 7 |
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.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (autifyhq-release) than the most recent previously approved version (riywo) on 2022-11-10, but autifyhq-release is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (autifyhq-release) than the most recent previously approved version (riywo) on 2022-11-02, but autifyhq-release is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (riywo) than the most recent previously approved version (autifyhq-release) on 2022-10-25, but riywo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.