@trigger.dev/sdk
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): Transition to GitHub Actions CI/CD publishing with SLSA provenance; stable for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level maintainer roster change; package has SLSA provenance and consistent repo. | ai | |
| dependencies | unvetted-dep:evt | AI (dependencies): evt is a well-known typed event emitter library; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:ulid | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Bundled SDK; ws is declared and used transitively, not directly imported at top level. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cronstrue | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:evt | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:slug | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.4.6 | 11 / 11 | |
| 4.4.5 | 11 / 11 | |
| 4.4.4 | 12 / 12 | |
| 4.4.3 | 12 / 12 | |
| 4.4.2 | 12 / 12 | |
| 4.4.1 | 12 / 12 | |
| 4.4.0 | 12 / 12 | |
| 4.3.3 | 12 / 12 | |
| 4.3.2 | 12 / 12 | |
| 4.3.1 | 12 / 12 | |
| 4.3.0 | 12 / 12 | |
| 4.2.0 | 12 / 12 | |
| 4.1.2 | 12 / 12 | |
| 4.1.1 | 12 / 12 | |
| 4.1.0 | 12 / 12 | |
| 4.0.7 | 12 / 12 | |
| 4.0.6 | 12 / 12 | |
| 4.0.5 | 12 / 12 | |
| 4.0.4 | 12 / 12 | |
| 4.0.3 | 12 / 12 | |
| 4.0.2 | 12 / 12 | |
| 4.0.1 | 12 / 12 | |
| 4.0.0 | 12 / 12 |
v4.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. 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.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicknpm) than the most recent previously approved version (ericallam) on 2025-11-03, but nicknpm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicknpm) than the most recent previously approved version (ericallam) on 2025-10-28, but nicknpm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.