@ifc-lite/parser
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publish (louistrue) to CI/CD (GitHub Actions) with SLSA attestation; this is a provenance improvement, not a compromise signal. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): @ifc-lite/parser is an IFC/BIM domain parser, not a typosquat of parcel; name similarity is coincidental. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 5 / 2 | |
| 3.9.1 | 5 / 2 | |
| 3.9.0 | 5 / 2 | |
| 3.8.5 | 5 / 2 | |
| 3.8.4 | 5 / 2 | |
| 3.8.3 | 5 / 2 | |
| 3.8.2 | 5 / 2 | |
| 3.8.1 | 5 / 2 | |
| 3.8.0 | 5 / 2 | |
| 3.7.0 | 5 / 2 | |
| 3.6.0 | 5 / 2 | |
| 3.5.2 | 4 / 2 | |
| 3.5.1 | 4 / 2 | |
| 3.5.0 | 4 / 2 | |
| 3.4.1 | 4 / 2 | |
| 3.4.0 | 4 / 2 | |
| 3.3.2 | 4 / 2 | |
| 3.3.1 | 4 / 2 | |
| 3.3.0 | 4 / 2 | |
| 3.2.0 | 4 / 2 | |
| 3.1.3 | 4 / 2 | |
| 3.1.2 | 4 / 2 | |
| 3.1.1 | 4 / 2 | |
| 3.1.0 | 4 / 2 | |
| 3.0.0 | 4 / 2 | |
| 2.4.2 | 4 / 2 | |
| 2.4.1 | 4 / 2 | |
| 2.4.0 | 4 / 2 | |
| 2.3.0 | 3 / 2 | |
| 2.2.0 | 3 / 2 | |
| 2.1.9 | 3 / 2 | |
| 2.1.8 | 3 / 2 | |
| 2.1.7 | 3 / 2 | |
| 2.1.6 | 3 / 2 | |
| 2.1.5 | 3 / 2 | |
| 2.1.4 | 3 / 2 | |
| 2.1.3 | 3 / 2 | |
| 2.1.2 | 3 / 2 | |
| 2.1.1 | 3 / 2 | |
| 2.1.0 | 3 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.14.3 | 2 / 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 | |
| 1.3.0 | 2 / 2 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.7 | 1 / 1 | |
| 1.1.6 | 1 / 1 | |
| 1.1.4 | 1 / 1 | |
| 1.1.3 | 1 / 1 | |
| 1.1.2 | 1 / 1 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. 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.
v3.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. 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.
v3.5.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-02. 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.
v3.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-29. 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.
v3.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-27. 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.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.