← Home

@ifc-lite/mutations

npm Repository Homepage

Mutation tracking and property editing for IFC-Lite

25
Versions
MPL-2.0
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

ifcbimmutationspropertiesaec

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ifc-lite/parser AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic fires as false positive for intra-workspace deps. ai
provenance no-provenance AI (provenance): Young monorepo package; provenance not yet configured but no other risk signals present. ai

Versions (showing 25 of 25)

Version Deps Published
1.21.0 2 / 2
1.20.0 2 / 2
1.19.0 2 / 2
1.15.0 1 / 2
1.14.5 1 / 2
1.14.4 1 / 2
1.14.3 1 / 2
1.14.2 2 / 2
1.14.1 2 / 2
1.14.0 2 / 2
1.13.0 2 / 2
1.11.5 2 / 2
1.11.4 2 / 2
1.11.3 2 / 2
1.11.2 2 / 2
1.11.1 2 / 2
1.11.0 2 / 2
1.10.0 2 / 2
1.9.0 2 / 2
1.8.0 2 / 2
1.7.0 2 / 2
1.6.1 2 / 2
1.6.0 2 / 2
1.5.0 2 / 2
1.4.0 2 / 2

v1.21.0

1 finding
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.

v1.20.0

1 finding
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.

v1.19.0

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-11, 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-11, 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.