@open-tender/types

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 2026-04-09, 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.

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-22, 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.

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.

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.

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.

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-09-03, 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.

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-08-20, 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.

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.

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.

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.

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.

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.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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

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-06, 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-04, 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-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: 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.

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.

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.

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

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 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: 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-12-04, 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-12-03, 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-12-03, 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-12-03, 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 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-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: 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-21, 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-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-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 2024-11-08, 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-08, 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-08, 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.

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.

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 2024-09-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: 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-09-23, 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-09-23, 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-09-23, 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-09-16, 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-09-16, 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-09-16, 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-09-03, 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-08-23, 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-08-23, 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: jcharrington.

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

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

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

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

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

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