@stdlib/utils-global
Return the global object.
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only test dependency URL pin, not shipped to consumers. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Hardcoded 'return this;' literal for global detection — standard pattern, no dynamic input, stable across versions. | ai | |
| phantom-deps | phantom-dep:@stdlib/error-tools-fmtprodmsg | AI (phantom-deps): Same-org stdlib dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 3 / 0 | |
| 0.2.2 | 3 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 3 / 6 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 | |
| 0.0.7 | 1 / 5 | |
| 0.0.6 | 1 / 5 | |
| 0.0.5 | 1 / 5 | |
| 0.0.4 | 1 / 5 | |
| 0.0.3 | 1 / 5 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.