@3dsource/angular-unreal-module
Angular Unreal module for connect with unreal engine stream
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Minor publish-env variance from a trusted, high-volume publisher; no behavioral evidence of tampering. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a well-known, benign utility dependency. | ai | |
| source-diff | obfuscated-file:types/3dsource-angular-unreal-module.d.ts | AI (source-diff): Long-line .d.ts files are normal Angular compiler output; not obfuscation. | ai | |
| source-diff | obfuscated-file:js/region-ping-prefetch.js | AI (source-diff): Minified region-ping utility fetching from 3dsource's own datacenter endpoint; no malicious patterns. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): 197 versions published; rapid CI-driven publishes are the established pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 51 of 132)
| Version | Deps | Published |
|---|---|---|
| 0.0.155 | 2 / 0 | |
| 0.0.154 | 1 / 0 | |
| 0.0.152 | 1 / 0 | |
| 0.0.151 | 1 / 0 | |
| 0.0.150 | 1 / 0 | |
| 0.0.149 | 1 / 0 | |
| 0.0.148 | 1 / 0 | |
| 0.0.145 | 1 / 0 | |
| 0.0.144 | 1 / 0 | |
| 0.0.143 | 1 / 0 | |
| 0.0.142 | 1 / 0 | |
| 0.0.141 | 1 / 0 | |
| 0.0.139 | 1 / 0 | |
| 0.0.138 | 1 / 0 | |
| 0.0.137 | 1 / 0 | |
| 0.0.136 | 1 / 0 | |
| 0.0.135 | 1 / 0 | |
| 0.0.134 | 1 / 0 | |
| 0.0.133 | 1 / 0 | |
| 0.0.132 | 1 / 0 | |
| 0.0.131 | 1 / 0 | |
| 0.0.128 | 1 / 0 | |
| 0.0.127 | 1 / 0 | |
| 0.0.125 | 1 / 0 | |
| 0.0.124 | 1 / 0 | |
| 0.0.123 | 1 / 0 | |
| 0.0.122 | 1 / 0 | |
| 0.0.121 | 1 / 0 | |
| 0.0.120 | 1 / 0 | |
| 0.0.119 | 1 / 0 | |
| 0.0.118 | 1 / 0 | |
| 0.0.117 | 1 / 0 | |
| 0.0.116 | 1 / 0 | |
| 0.0.115 | 1 / 0 | |
| 0.0.114 | 1 / 0 | |
| 0.0.113 | 1 / 0 | |
| 0.0.112 | 1 / 0 | |
| 0.0.111 | 1 / 0 | |
| 0.0.110 | 1 / 0 | |
| 0.0.109 | 1 / 0 | |
| 0.0.108 | 1 / 0 | |
| 0.0.107 | 1 / 0 | |
| 0.0.106 | 1 / 0 | |
| 0.0.105 | 1 / 0 | |
| 0.0.103 | 1 / 0 | |
| 0.0.102 | 1 / 0 | |
| 0.0.101 | 1 / 0 | |
| 0.0.100 | 1 / 0 | |
| 0.0.99 | 1 / 0 | |
| 0.0.98 | 1 / 0 | |
| 0.0.97 | 1 / 0 |
v0.0.155
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: andrei.parcheuski.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.150
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (andrei.parcheuski) than the most recent previously approved version (flashpusher) on 2026-07-15, but andrei.parcheuski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.149
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (flashpusher) than the most recent previously approved version (andrei.parcheuski) on 2026-07-13, but flashpusher is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.148
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.