@ember-data/request-utils
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the ember-data monorepo; mass-production signal reflects monorepo structure, not spam. | ai | |
| typosquat | typosquat.pattern:request | AI (typosquat): Legitimate EmberData utility package; 'request' in the name reflects its purpose, not impersonation of the npm 'request' package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.8.2 | 3 / 9 | |
| 5.8.1 | 3 / 9 | |
| 5.7.0 | 3 / 9 | |
| 5.6.0 | 3 / 9 | |
| 5.5.0 | 2 / 13 | |
| 5.4.1 | 2 / 12 | |
| 5.3.13 | 2 / 12 | |
| 5.3.12 | 2 / 12 | |
| 5.3.11 | 2 / 13 | |
| 5.3.10 | 2 / 13 | |
| 5.3.9 | 2 / 13 | |
| 5.3.8 | 2 / 13 | |
| 5.3.7 | 2 / 13 | |
| 5.3.6 | 2 / 13 | |
| 5.3.5 | 2 / 13 | |
| 5.3.4 | 2 / 13 |
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.