← Home

delims

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jonschlinkertdoowb

Keywords

boundariescustomcustomizedelimitersdelimsexpressionsfrontmatterpatternpatternsreregexregexpregulartemplatetemplatesyamlyfm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package is ~12 years old, predating Sigstore provenance on npm. No provenance is expected and not a security concern for this package. ai
phantom-deps phantom-dep:yfm AI (phantom-deps): yfm is a legitimate YAML front matter utility consistent with this package's purpose; phantom usage is a minor hygiene issue, not a security risk. ai
phantom-deps phantom-dep:fs-utils AI (phantom-deps): fs-utils appears in both dependencies and devDependencies; phantom usage in config files is a minor hygiene issue, not a security risk. ai

Versions (showing 10 of 10)

Version Deps Published
0.4.2 3 / 2
0.4.1 3 / 2
0.4.0 3 / 4
0.3.0 2 / 2
0.2.0 2 / 2
0.1.4 1 / 2
0.1.3 1 / 2
0.1.2 2 / 4
0.1.1 3 / 4
0.1.0 3 / 4

v0.4.2

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.

v0.4.1

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.

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.4

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.

v0.1.3

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.

v0.1.2

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.

v0.1.1

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.

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.