@nanoforge-dev/core-editor
NanoForge Engine - Core Editor
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:class-validator | AI (phantom-deps): Config-referenced transitive dep; stable for this package. | ai | |
| phantom-deps | phantom-dep:class-transformer | AI (phantom-deps): Config-referenced transitive dep; stable for this package. | ai | |
| phantom-deps | phantom-dep:@nanoforge-dev/input | AI (phantom-deps): Same-org scope dep; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@nanoforge-dev/ecs-client | AI (phantom-deps): Same-org scope dep; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@nanoforge-dev/asset-manager | AI (phantom-deps): Same-org scope dep; likely re-exported or used indirectly. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 6 / 10 | |
| 1.3.0 | 6 / 10 | |
| 1.0.2 | 6 / 9 | |
| 1.0.1 | 6 / 9 | |
| 1.0.0 | 6 / 9 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.