stentor-models
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 51 of 96)
| Version | Deps | Published |
|---|---|---|
| 1.74.0 | 1 / 6 | |
| 1.73.0 | 1 / 6 | |
| 1.72.4 | 1 / 6 | |
| 1.72.3 | 1 / 6 | |
| 1.72.0 | 1 / 6 | |
| 1.71.0 | 1 / 6 | |
| 1.69.14 | 1 / 6 | |
| 1.69.9 | 1 / 6 | |
| 1.69.7 | 1 / 6 | |
| 1.69.6 | 1 / 6 | |
| 1.69.0 | 1 / 6 | |
| 1.68.23 | 1 / 6 | |
| 1.68.6 | 1 / 6 | |
| 1.67.0 | 1 / 6 | |
| 1.66.50 | 1 / 6 | |
| 1.66.49 | 1 / 6 | |
| 1.66.46 | 1 / 6 | |
| 1.66.41 | 1 / 6 | |
| 1.66.35 | 1 / 6 | |
| 1.66.30 | 1 / 6 | |
| 1.66.25 | 1 / 6 | |
| 1.66.24 | 1 / 6 | |
| 1.66.22 | 1 / 6 | |
| 1.66.12 | 1 / 6 | |
| 1.66.10 | 1 / 6 | |
| 1.66.0 | 1 / 6 | |
| 1.65.9 | 1 / 6 | |
| 1.65.7 | 1 / 6 | |
| 1.64.0 | 1 / 6 | |
| 1.61.16 | 1 / 6 | |
| 1.61.11 | 1 / 6 | |
| 1.61.9 | 1 / 6 | |
| 1.61.7 | 1 / 6 | |
| 1.61.2 | 1 / 6 | |
| 1.61.1 | 1 / 6 | |
| 1.60.59 | 1 / 6 | |
| 1.60.55 | 1 / 6 | |
| 1.60.48 | 1 / 6 | |
| 1.60.45 | 1 / 6 | |
| 1.60.44 | 1 / 6 | |
| 1.60.38 | 1 / 6 | |
| 1.60.35 | 1 / 6 | |
| 1.60.31 | 1 / 6 | |
| 1.60.29 | 1 / 6 | |
| 1.60.26 | 1 / 6 | |
| 1.60.24 | 1 / 6 | |
| 1.60.23 | 1 / 6 | |
| 1.60.22 | 1 / 6 | |
| 1.60.20 | 1 / 6 | |
| 1.60.16 | 1 / 6 | |
| 1.60.15 | 1 / 6 |
v1.74.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (michaelmyers) on 2026-07-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.