@open-tender/utils

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: luong-iacm.

This version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.

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

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: luong-iacm.

This 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.

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

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

This version was published by a different npm account (shady.abdelaziz.farahat) than the most recent previously approved version (nasser_md) on 2025-10-28, but shady.abdelaziz.farahat 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-04-22, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-04-18, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-04-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-04-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-03-31, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-03-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-24, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-18, but nasser_md 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.

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

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-14, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-13, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-02-13, but nasser_md 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.

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

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

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-30, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-30, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-30, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-30, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-24, but vaulis11 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.

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

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

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-20, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-20, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-17, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-16, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-14, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-07, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-02, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-02, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2025-01-02, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-12-24, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-12-19, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-12-09, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-12-06, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-25, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-21, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-15, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-15, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nasser_md.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-15, but nasser_md 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-11-15, but vaulis11 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joshua-nord.

This version was published by a different npm account than previous versions on 2024-10-28. This could indicate a legitimate maintainer transition or an account compromise.

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

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vaulis11.

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

This version was published by a different npm account (vaulis11) than the most recent previously approved version (shady.abdelaziz.farahat) on 2024-10-14, but vaulis11 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.

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

This version was published by a different npm account (shady.abdelaziz.farahat) than the most recent previously approved version (nasser_md) on 2024-10-08, but shady.abdelaziz.farahat 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.

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

This version was published by a different npm account (nasser_md) than the most recent previously approved version (vaulis11) on 2024-10-07, but nasser_md 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.