@renseiai/create-agentfactory-app
Create an AgentFactory app — multi-agent fleet management for coding agents
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 manual publish to GitHub Actions CI with SLSA attestation; legitimate workflow change for this package. | ai | |
| provenance | missing-githead | AI (provenance): CI-based publish via GitHub Actions does not always populate gitHead; SLSA attestation provides stronger commit linkage. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 0 / 3 | |
| 0.8.66 | 0 / 3 | |
| 0.8.65 | 0 / 3 | |
| 0.8.63 | 0 / 3 | |
| 0.8.62 | 0 / 3 | |
| 0.8.60 | 0 / 3 | |
| 0.8.59 | 0 / 3 | |
| 0.8.58 | 0 / 3 | |
| 0.8.57 | 0 / 3 | |
| 0.8.56 | 0 / 3 | |
| 0.8.55 | 0 / 3 | |
| 0.8.54 | 0 / 3 | |
| 0.8.53 | 0 / 3 | |
| 0.8.52 | 0 / 3 | |
| 0.8.51 | 0 / 3 | |
| 0.8.50 | 0 / 3 | |
| 0.8.49 | 0 / 3 | |
| 0.8.48 | 0 / 3 | |
| 0.8.46 | 0 / 3 | |
| 0.8.45 | 0 / 3 | |
| 0.8.44 | 0 / 3 | |
| 0.8.43 | 0 / 3 | |
| 0.8.42 | 0 / 3 | |
| 0.8.41 | 0 / 3 | |
| 0.8.40 | 0 / 3 | |
| 0.8.39 | 0 / 3 | |
| 0.8.38 | 0 / 3 | |
| 0.8.37 | 0 / 3 | |
| 0.8.36 | 0 / 3 | |
| 0.8.35 | 0 / 3 | |
| 0.8.34 | 0 / 3 | |
| 0.8.33 | 0 / 3 | |
| 0.8.32 | 0 / 3 | |
| 0.8.31 | 0 / 3 | |
| 0.8.30 | 0 / 3 | |
| 0.8.29 | 0 / 3 | |
| 0.8.28 | 0 / 3 | |
| 0.8.27 | 0 / 3 | |
| 0.8.26 | 0 / 3 | |
| 0.8.25 | 0 / 3 | |
| 0.8.24 | 0 / 3 | |
| 0.8.23 | 0 / 3 | |
| 0.8.22 | 0 / 3 | |
| 0.8.21 | 0 / 3 | |
| 0.8.20 | 0 / 3 | |
| 0.8.19 | 0 / 3 | |
| 0.8.18 | 0 / 3 | |
| 0.8.17 | 0 / 3 | |
| 0.8.16 | 0 / 3 | |
| 0.8.15 | 0 / 3 | |
| 0.8.14 | 0 / 3 |
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.18
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.17
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.16
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.15
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.14
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.