@gooddata/mock-js
Mock server for GoodData UI applications (Analytical Designer and Dashboards).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): GoodData org regularly rotates CI/developer maintainers; pattern is consistent across many approved versions. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same rotation pattern; removals paired with additions in an established org account. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Pattern is a cache-invalidation reload (delete require.cache then re-require same module); not user-controlled arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): @types packages are type-only and loaded by convention; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@types/seedrandom | AI (phantom-deps): @types packages are type-only and loaded by convention; not a real phantom dep risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.24.20 | 13 / 19 | |
| 2.24.19 | 13 / 19 | |
| 2.24.18 | 13 / 19 | |
| 2.24.17 | 13 / 19 | |
| 2.24.16 | 13 / 19 | |
| 2.24.15 | 13 / 19 |
v2.24.20
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.19
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.17
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.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.
v2.24.16
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.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.
v2.24.15
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.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.