@ifc-lite/encoding
19
Versions
—
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
louistrue
Keywords
ifcbimencodingstepaec
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.14.11 | 0 / 2 | |
| 1.14.6 | 0 / 2 | |
| 1.14.5 | 0 / 2 | |
| 1.14.4 | 0 / 2 | |
| 1.14.3 | 0 / 2 | |
| 1.14.2 | 0 / 2 | |
| 1.14.1 | 0 / 2 | |
| 1.14.0 | 0 / 2 | |
| 1.13.0 | 0 / 2 | |
| 1.11.5 | 0 / 2 | |
| 1.11.4 | 0 / 2 | |
| 1.11.3 | 0 / 2 | |
| 1.11.2 | 0 / 2 | |
| 1.11.1 | 0 / 2 | |
| 1.11.0 | 0 / 2 | |
| 1.10.0 | 0 / 2 | |
| 1.9.0 | 0 / 2 | |
| 1.8.0 | 0 / 2 | |
| 1.7.0 | 0 / 2 |
v1.14.11
2 findings
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.
INFO
Publisher changed: louistrue → GitHub Actions (on 2026-07-17, now via trusted publisher with provenance)
provenance
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (louistrue) on 2026-07-17, 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.