@directus/extensions-sdk
A toolkit to develop extensions to extend Directus
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Directus migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate maintainer transition for the org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; Directus monorepo release cadence explains gaps. | ai | |
| dependencies | unvetted-dep:@directus/constants | AI (dependencies): Internal Directus monorepo package; stable dependency for this SDK. | ai | |
| dependencies | unvetted-dep:rollup-plugin-styler | AI (dependencies): Standard build tooling dependency for extension bundling; no malicious indicators. | ai | |
| phantom-deps | phantom-dep:vite | AI (phantom-deps): vite is a declared runtime dep used as a build tool; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): esbuild is a declared dep used as a runtime binary; known implicit dependency pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Directus monorepo sub-package; sparse README/no keywords is normal for internal SDK packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 17.1.4 | 26 / 7 | |
| 17.1.3 | 26 / 7 | |
| 17.1.2 | 26 / 7 | |
| 17.1.1 | 26 / 7 | |
| 17.1.0 | 26 / 7 | |
| 17.0.11 | 26 / 7 | |
| 17.0.10 | 26 / 7 | |
| 17.0.9 | 26 / 7 | |
| 17.0.8 | 26 / 7 | |
| 17.0.7 | 26 / 7 | |
| 17.0.6 | 26 / 7 | |
| 17.0.5 | 26 / 7 | |
| 17.0.4 | 26 / 7 | |
| 17.0.3 | 26 / 7 | |
| 17.0.2 | 26 / 7 | |
| 17.0.1 | 26 / 7 | |
| 17.0.0 | 26 / 7 |
v17.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.4
2 findingsThis version was published by a different npm account than previous versions on 2025-12-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v17.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.