@pie-framework/pie-configure-events
Supply chain provenance
Status for the latest visible version.
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
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 0 / 2 | |
| 1.4.0 | 0 / 2 | |
| 1.3.1 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.0 | 0 / 2 |
v1.4.0
2 findingsThis version was published by a different npm account (andreeapescar) than the most recent previously approved version (iacoshoria) on 2023-05-15. It has since remained available on npm for 1165 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version was published by a different npm account (andreeapescar) than the most recent previously approved version (iacoshoria) on 2023-05-15. It has since remained available on npm for 1165 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.