← Home

@remix-run/terminal

npm Repository Homepage

Placeholder package for Remix CI/OIDC setup

3
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

mjackson

Keywords

terminalansicolorsclioutput

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): remix-run org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI/CD pipeline. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Intentional placeholder package by official Remix maintainer; 0.0.0 is expected. ai
bogus-package bogus-package AI (bogus-package): Legitimate CI/OIDC placeholder from the remix-run org; no-deps and tiny payload are by design. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.1 0 / 2
0.1.0 0 / 2
0.0.0 0 / 0

v0.1.1

2 findings
HIGH Publisher changed: mjackson → GitHub Actions (on 2026-05-20) provenance

This version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

2 findings
HIGH Publisher changed: mjackson → GitHub Actions (on 2026-04-29) provenance

This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.