@gooddata/sdk-pluggable-application-model
GoodData SDK model contracts for pluggable applications
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@gooddata/sdk-model | AI (dependencies): Sibling GoodData SDK package at matching version; part of the same monorepo release. | ai | |
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): Stale maintainer email on an established GoodData SDK package; active publisher gooddata-ci has strong track record. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-invariant | AI (phantom-deps): Referenced in config files per finding; stable false positive for this SDK package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SDK model contracts library; minimal README and no keywords are expected for internal SDK packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 3 / 23 | |
| 11.39.0 | 3 / 23 | |
| 11.38.0 | 3 / 23 | |
| 11.37.0 | 3 / 23 | |
| 11.36.0 | 3 / 23 | |
| 11.35.0 | 3 / 23 | |
| 11.34.0 | 4 / 23 | |
| 11.33.0 | 4 / 23 | |
| 11.32.0 | 4 / 23 | |
| 11.31.0 | 4 / 23 | |
| 11.30.0 | 4 / 23 | |
| 11.29.0 | 4 / 23 | |
| 11.28.0 | 4 / 23 | |
| 11.27.0 | 4 / 23 | |
| 11.26.0 | 4 / 23 | |
| 11.25.0 | 4 / 23 |
v11.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.30.0
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.
v11.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.28.0
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.
v11.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.26.0
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.
v11.25.0
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.