@automattic/jetpack-ai-client
A JS client for consuming Jetpack AI services
Supply chain provenance
Status for the latest visible version.
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): Automattic org package; new maintainers are consistent with org contributors, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @wordpress/ui is a first-party WordPress package; low risk for this WordPress-ecosystem client. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@automattic/jetpack-explat | AI (dependencies): Same org scope (Automattic); workspace dependency expected in monorepo context. | ai | |
| phantom-deps | phantom-dep:@automattic/jetpack-connection | AI (phantom-deps): Same-org peer dependency; stable pattern for Automattic monorepo packages. | ai | |
| phantom-deps | phantom-dep:@automattic/jetpack-explat | AI (phantom-deps): Same-org package declared as dependency; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package from Automattic; sparse README and no keywords are expected for internal JS packages. | ai | |
| phantom-deps | phantom-dep:@automattic/jetpack-base-styles | AI (phantom-deps): Same-org package declared as dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/wordpress__block-editor | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/runtime dep declared in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@types/jest | AI (phantom-deps): Framework-scoped type package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): Referenced in config files; stable false positive for this monorepo package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.34.18 | 31 / 9 | |
| 0.34.12 | 30 / 9 | |
| 0.34.10 | 30 / 9 | |
| 0.34.9 | 30 / 9 | |
| 0.34.7 | 30 / 8 | |
| 0.34.1 | 30 / 8 | |
| 0.33.22 | 30 / 9 | |
| 0.33.17 | 30 / 9 | |
| 0.33.12 | 30 / 9 | |
| 0.33.11 | 30 / 9 | |
| 0.33.10 | 30 / 9 | |
| 0.33.7 | 30 / 9 | |
| 0.33.2 | 30 / 9 | |
| 0.33.1 | 30 / 10 | |
| 0.33.0 | 30 / 10 | |
| 0.31.2 | 28 / 10 | |
| 0.31.1 | 28 / 10 | |
| 0.29.0 | 28 / 10 | |
| 0.28.1 | 28 / 10 | |
| 0.28.0 | 28 / 10 | |
| 0.27.10 | 28 / 10 | |
| 0.27.9 | 28 / 10 |
v0.34.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.