@galacean/engine-loader
A subpackage of `@galacean/engine`.
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:yufangjun.com | AI (email-domain): SLSA provenance attestation provides stronger identity assurance; risk of domain hijack is mitigated for this established package. | ai | |
| phantom-deps | phantom-dep:@galacean/engine-core | AI (phantom-deps): Same-org monorepo peer dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@galacean/engine-math | AI (phantom-deps): Same-org monorepo peer dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@galacean/engine-rhi-webgl | AI (phantom-deps): Same-org monorepo peer dependency; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are expected for internal engine modules. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.6.12 | 3 / 0 | |
| 1.6.11 | 3 / 0 | |
| 1.6.10 | 3 / 0 | |
| 1.6.9 | 3 / 0 | |
| 1.6.8 | 3 / 0 | |
| 1.6.7 | 3 / 0 | |
| 1.6.6 | 3 / 0 | |
| 1.6.5 | 3 / 0 | |
| 1.6.4 | 3 / 0 | |
| 1.6.3 | 3 / 0 | |
| 1.6.2 | 3 / 0 | |
| 1.6.1 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.16 | 3 / 0 | |
| 1.5.15 | 3 / 0 | |
| 1.5.14 | 3 / 0 | |
| 1.5.13 | 3 / 0 | |
| 1.5.12 | 3 / 0 | |
| 1.5.11 | 3 / 0 | |
| 1.5.10 | 3 / 0 | |
| 1.5.9 | 3 / 0 | |
| 1.5.8 | 3 / 0 | |
| 1.5.7 | 3 / 0 | |
| 1.5.6 | 3 / 0 | |
| 1.5.5 | 3 / 0 | |
| 1.5.4 | 3 / 0 | |
| 1.5.3 | 3 / 0 | |
| 1.5.2 | 3 / 0 | |
| 1.5.1 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.16 | 3 / 0 | |
| 1.1.6 | 4 / 0 |
v1.6.12
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.11
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.10
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.9
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.16
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.15
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.14
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.13
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.12
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.11
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.10
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.9
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.16
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.