← Home

@crowdfarming/oliva-ds

npm

Librería de componentes de diseño de Oliva

98
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

moisesacgtie_crowdfarmingjjbalso_cfcrowdfarming_admind.corralesv.serranoalberto.gilalexmdvcf-ddgcarbayojacanoggomez2agomezmarti.riberafermedinamiguel.vinascf-victorcf-s.duquesara.lopezcf-thibaudgraham_cfcf-c.nuneza.huertasrafael-cfcf-j.martinezcf-vmunozcf-f.martinscf-p.agudocf-j.salvadorcf-d.martincf-j.garciacf-i.cortescf-j.bajanacf-j.mbarrigacf-o.olabicf-y.delacortecf-e.vega2cf-g.carvalhocf-g.cruzcf_josevivancocrowdfarmingcf-l.asenjocf-acorregidorcf-artzaicf-n.milville

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org-managed package with rotating internal team maintainers, publisher confirmed known maintainer. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with internal team turnover, not a takeover pattern. ai
source-diff source-size-tripled AI (source-diff): Growth from bundled font/theme assets, not injected code. ai
source-diff large-new-source-files AI (source-diff): New files are fonts/CSS themes, consistent with design-system package. ai
bogus-package bogus-package AI (bogus-package): Internal design-system lib for crowdfarming.com, not spam. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard Angular compiler implicit dependency; not a real phantom dep for Angular libraries. ai

Versions (showing 98 of 98)

Version Deps Published
1.103.0 1 / 0
1.102.0 1 / 0
1.101.0 1 / 0
1.100.0 1 / 0
1.99.0 1 / 0
1.98.0 1 / 0
1.97.1 1 / 0
1.97.0 1 / 0
1.96.0 1 / 0
1.95.0 1 / 0
1.94.0 1 / 0
1.93.0 1 / 0
1.92.0 1 / 0
1.91.0 1 / 0
1.90.0 1 / 0
1.89.0 1 / 0
1.88.0 1 / 0
1.87.1 1 / 0
1.87.0 1 / 0
1.86.0 1 / 0
1.85.0 1 / 0
1.84.0 1 / 0
1.83.0 1 / 0
1.82.0 1 / 0
1.81.0 1 / 0
1.80.0 1 / 0
1.79.0 1 / 0
1.78.0 1 / 0
1.77.0 1 / 0
1.76.0 1 / 0
1.75.0 1 / 0
1.74.0 1 / 0
1.73.0 1 / 0
1.72.0 1 / 0
1.71.0 1 / 0
1.70.0 1 / 0
1.69.0 1 / 0
1.68.3 1 / 0
1.68.2 1 / 0
1.68.1 1 / 0
1.68.0 1 / 0
1.67.0 1 / 0
1.66.0 1 / 0
1.65.0 1 / 0
1.64.0 1 / 0
1.63.0 1 / 0
1.62.0 1 / 0
1.61.0 1 / 0
1.60.0 1 / 0
1.59.0 1 / 0
1.58.0 1 / 0
1.57.0 1 / 0
1.56.0 1 / 0
1.55.1 1 / 0
1.55.0 1 / 0
1.54.0 1 / 0
1.53.0 1 / 0
1.52.0 1 / 0
1.51.0 1 / 0
1.50.0 1 / 0
1.49.0 1 / 0
1.48.0 1 / 0
1.47.0 1 / 0
1.46.2 1 / 0
1.46.1 1 / 0
1.46.0 1 / 0
1.45.0 1 / 0
1.44.1 1 / 0
1.44.0 1 / 0
1.43.0 1 / 0
1.42.2 1 / 0
1.42.1 1 / 0
1.42.0 1 / 0
1.41.0 1 / 0
1.40.0 1 / 0
1.39.0 1 / 0
1.38.0 1 / 0
1.37.0 1 / 0
1.36.0 1 / 0
1.35.0 1 / 0
1.34.0 1 / 0
1.10.0 1 / 0
1.9.0 1 / 0
1.8.0 1 / 0
1.7.1 1 / 0
1.7.0 1 / 0
1.6.0 1 / 0
1.5.0 1 / 0
1.4.0 1 / 0
1.3.5 1 / 0
1.3.4 1 / 0
1.3.3 1 / 0
1.3.2 0 / 0
1.3.1 1 / 0
1.3.0 1 / 0
1.2.2 1 / 0
1.2.1 1 / 0
1.2.0 1 / 0

v1.103.0

1 finding
LOW No provenance attestation provenance

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

v1.102.0

1 finding
LOW No provenance attestation provenance

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

v1.101.0

1 finding
LOW No provenance attestation provenance

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

v1.100.0

1 finding
LOW No provenance attestation provenance

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

v1.99.0

1 finding
LOW No provenance attestation provenance

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

v1.98.0

1 finding
LOW No provenance attestation provenance

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

v1.97.1

1 finding
LOW No provenance attestation provenance

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

v1.95.0

1 finding
LOW No provenance attestation provenance

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

v1.78.0

1 finding
LOW No provenance attestation provenance

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

v1.77.0

1 finding
LOW No provenance attestation provenance

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

v1.76.0

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: cf-ddgcarbayo → cf-d.martin (on 2026-04-09, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (cf-ddgcarbayo) on 2026-04-09, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.75.0

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: jjbalso_cf → cf-d.martin (on 2026-03-23, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-03-23, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.74.0

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: jjbalso_cf → cf-d.martin (on 2026-03-18, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-03-18, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.73.0

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: jjbalso_cf → cf-d.martin (on 2026-03-10, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-03-10, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.72.0

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: jjbalso_cf → cf-d.martin (on 2026-03-09, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-03-09, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.71.0

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: jjbalso_cf → cf-d.martin (on 2026-03-03, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-03-03, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.70.0

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: jjbalso_cf → cf-d.martin (on 2026-02-23, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-23, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.69.0

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: jjbalso_cf → cf-d.martin (on 2026-02-19, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-19, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.68.3

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: jjbalso_cf → cf-d.martin (on 2026-02-17, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-17, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.68.2

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: jjbalso_cf → cf-d.martin (on 2026-02-16, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-16, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.68.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: jjbalso_cf → cf-d.martin (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-11, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.68.0

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: jjbalso_cf → cf-d.martin (on 2026-02-10, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-10, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.67.0

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: jjbalso_cf → cf-d.martin (on 2026-02-09, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-09, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.66.0

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: jjbalso_cf → cf-d.martin (on 2026-02-09, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-09, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.65.0

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: jjbalso_cf → cf-d.martin (on 2026-02-03, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-02-03, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.64.0

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: jjbalso_cf → cf-d.martin (on 2026-01-30, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-30, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.63.0

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: jjbalso_cf → cf-d.martin (on 2026-01-29, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-29, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.62.0

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: jjbalso_cf → cf-d.martin (on 2026-01-27, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-27, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.61.0

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: jjbalso_cf → cf-d.martin (on 2026-01-22, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-22, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.60.0

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: jjbalso_cf → cf-d.martin (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-21, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.59.0

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: jjbalso_cf → cf-d.martin (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-21, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.58.0

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: jjbalso_cf → cf-d.martin (on 2026-01-15, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-15, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.57.0

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: jjbalso_cf → cf-d.martin (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-14, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.56.0

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: jjbalso_cf → cf-d.martin (on 2026-01-08, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2026-01-08, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.55.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: jjbalso_cf → cf-d.martin (on 2025-12-26, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-26, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.55.0

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: jjbalso_cf → cf-d.martin (on 2025-12-24, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-24, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.54.0

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: jjbalso_cf → cf-d.martin (on 2025-12-24, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-24, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.53.0

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: jjbalso_cf → cf-d.martin (on 2025-12-22, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-22, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.52.0

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: jjbalso_cf → cf-d.martin (on 2025-12-19, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-19, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.51.0

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: jjbalso_cf → cf-d.martin (on 2025-12-15, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-15, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.50.0

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: jjbalso_cf → cf-d.martin (on 2025-12-15, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-15, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.49.0

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: jjbalso_cf → cf-d.martin (on 2025-12-12, known maintainer) provenance

This version was published by a different npm account (cf-d.martin) than the most recent previously approved version (jjbalso_cf) on 2025-12-12, but cf-d.martin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.48.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-05, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-05, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.47.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-04, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-04, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.46.2

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-04, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-04, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.46.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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-03, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-03, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.46.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-03, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-03, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.45.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-03, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-03, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.44.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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-02, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-02, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.44.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-12-01, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-12-01, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.43.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-28, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-28, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.42.2

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-25, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-25, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.42.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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-23, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-23, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.42.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-23, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-23, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.41.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-18, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-18, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.40.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-18, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-18, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.39.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-14, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-14, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.38.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-12, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-12, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.37.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-04, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-04, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.36.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-11-03, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-11-03, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.35.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-10-31, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-10-31, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.34.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-10-31, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-10-31, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.1

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

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: jjbalso_cf → cf-ddgcarbayo (on 2025-06-04, known maintainer) provenance

This version was published by a different npm account (cf-ddgcarbayo) than the most recent previously approved version (jjbalso_cf) on 2025-06-04, but cf-ddgcarbayo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.