@directus/types
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@directus/ai | AI (dependencies): First-party @directus/* scoped package from the same monorepo; not a third-party risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Routine maintainer rotation in the Directus org; no malware signals. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Directus transitioned to automated CI publishing; individual maintainer removal is expected and consistent with the SLSA-attested workflow. | ai | |
| provenance | publisher-changed | AI (provenance): Directus monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/archiver is a DefinitelyTyped type-only package; consistent with this package's existing @types/* runtime dep pattern. | ai | |
| dependencies | unvetted-dep:@directus/constants | AI (dependencies): Internal sibling package from the same Directus monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@directus/schema | AI (dependencies): Internal sibling package from the same Directus monorepo; expected dependency pattern. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only declaration in a types package; not imported directly by design. | ai | |
| phantom-deps | phantom-dep:@types/nodemailer | AI (phantom-deps): Type-only declaration in a types package; not imported directly by design. | ai | |
| phantom-deps | phantom-dep:@types/archiver | AI (phantom-deps): Type-only declaration in a types package; not imported directly by design. | ai | |
| phantom-deps | phantom-dep:@types/geojson | AI (phantom-deps): Type-only declaration in a types package; not imported directly by design. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only declaration in a types package; not imported directly by design. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 15.0.3 | 9 / 6 | |
| 15.0.2 | 9 / 6 | |
| 15.0.1 | 10 / 6 | |
| 15.0.0 | 10 / 6 | |
| 14.3.1 | 10 / 5 | |
| 14.2.1 | 10 / 5 | |
| 14.1.0 | 10 / 5 | |
| 14.0.0 | 8 / 6 | |
| 13.5.0 | 8 / 6 | |
| 13.4.0 | 7 / 6 | |
| 13.3.1 | 7 / 6 |
v15.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-30. 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.
v15.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. 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.
v14.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. 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.
v14.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-16. 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.
v14.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. 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.
v14.0.0
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.
v13.5.0
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.
v13.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v13.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.