@eforge-build/engine
Autonomous plan-build-review orchestration engine. Implementation detail of @eforge-build/eforge - not intended for direct consumption.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai | |
| phantom-deps | phantom-dep:@eforge-build/client | AI (phantom-deps): Same-org sibling package; likely used indirectly via re-exports rather than direct import. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): Declared in package.json; likely used in compiled dist output not visible to static import analysis. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared in package.json; likely used in compiled dist output not visible to static import analysis. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.7.12 | 13 / 3 | |
| 0.7.11 | 13 / 3 | |
| 0.7.10 | 13 / 3 | |
| 0.7.9 | 13 / 3 | |
| 0.7.8 | 12 / 3 | |
| 0.7.7 | 12 / 3 | |
| 0.7.6 | 12 / 3 | |
| 0.7.4 | 12 / 3 | |
| 0.7.3 | 12 / 3 | |
| 0.7.2 | 12 / 3 | |
| 0.7.1 | 12 / 3 | |
| 0.7.0 | 12 / 3 | |
| 0.6.2 | 12 / 3 | |
| 0.6.0 | 12 / 3 | |
| 0.5.12 | 12 / 3 | |
| 0.5.11 | 12 / 3 | |
| 0.5.10 | 12 / 3 | |
| 0.5.8 | 12 / 3 | |
| 0.5.6 | 12 / 3 | |
| 0.5.4 | 12 / 3 | |
| 0.5.3 | 12 / 3 | |
| 0.5.2 | 12 / 3 | |
| 0.5.1 | 12 / 3 | |
| 0.5.0 | 12 / 3 |
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.