@ai-rpg-engine/cli
AI RPG Engine developer CLI: run, validate, replay, inspect, scaffold
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped monorepo package @ai-rpg-engine/cli; Levenshtein match to 'joi' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@ai-rpg-engine/core | AI (phantom-deps): Same-org sibling dep; likely re-exported or used transitively in CLI tooling. | ai | |
| phantom-deps | phantom-dep:@ai-rpg-engine/modules | AI (phantom-deps): Same-org sibling dep; same rationale as @ai-rpg-engine/core. | ai | |
| phantom-deps | phantom-dep:@ai-rpg-engine/content-schema | AI (phantom-deps): Same-org sibling dep; same rationale as @ai-rpg-engine/core. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 16 / 0 | |
| 2.0.9 | 16 / 0 | |
| 2.0.8 | 16 / 0 | |
| 2.0.7 | 16 / 0 | |
| 2.0.6 | 16 / 0 | |
| 2.0.5 | 16 / 0 | |
| 2.0.4 | 16 / 0 | |
| 2.0.3 | 13 / 0 | |
| 2.0.2 | 13 / 0 | |
| 2.0.1 | 13 / 0 | |
| 2.0.0 | 5 / 0 | |
| 1.0.1 | 5 / 0 | |
| 1.0.0 | 5 / 0 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.