← Home

@one-ini/wasm

npm Repository Homepage

Parse EditorConfig-INI file contents into AST

6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

florianbhildjj

Keywords

editorconfiginiparserast

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions as part of a legitimate CI/CD migration; SLSA provenance attestation confirms the release was built from the official one-ini/core repo. ai
publish-pattern dormant-publish AI (publish-pattern): Low-activity utility package; dormancy followed by a CI/CD-attested release is consistent with legitimate maintenance, not takeover. ai

Versions (showing 6 of 6)

Version Deps Published
0.2.1 0 / 0
0.2.0 0 / 0
0.1.3 0 / 0
0.1.2 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0

v0.2.1

2 findings
HIGH Publisher changed: hildjj → GitHub Actions (on 2026-02-23) provenance

This version was published by a different npm account than previous versions on 2026-02-23. 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.2.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.

v0.1.3

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.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: florianb → hildjj (on 2022-10-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-25. This could indicate a legitimate maintainer transition or an account compromise.

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