@golemio/pid
Golemio PID Module
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Shift to CI/CD-based publishing for same org, no behavior change in diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI/CD publishing takeover, no other malicious signal. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitLab CI/CD; Sigstore provenance not configured for this org's pipeline — stable false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @golemio org package; Levenshtein match to 'uuid' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @golemio org package; Levenshtein match to 'pino' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @golemio org package; Levenshtein match to 'pg' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @golemio org package; Levenshtein match to 'zod' is coincidental. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 5.17.2 | 8 / 39 | |
| 5.17.1 | 8 / 39 | |
| 5.17.0 | 8 / 39 | |
| 5.16.0 | 8 / 39 | |
| 5.15.3 | 8 / 39 | |
| 5.15.2 | 8 / 39 | |
| 5.15.1 | 8 / 39 | |
| 5.15.0 | 8 / 39 | |
| 5.14.1 | 8 / 39 | |
| 5.14.0 | 8 / 39 | |
| 5.13.0 | 8 / 39 | |
| 5.12.0 | 8 / 39 | |
| 5.11.0 | 8 / 39 | |
| 5.10.0 | 8 / 39 | |
| 5.9.2 | 7 / 39 | |
| 5.9.1 | 7 / 39 | |
| 5.9.0 | 7 / 39 | |
| 5.8.3 | 7 / 39 | |
| 5.8.2 | 7 / 39 | |
| 5.8.1 | 7 / 39 | |
| 5.8.0 | 7 / 39 | |
| 5.7.3 | 7 / 39 | |
| 5.7.2 | 7 / 39 | |
| 5.7.1 | 7 / 39 | |
| 5.7.0 | 7 / 39 | |
| 5.6.2 | 7 / 39 | |
| 5.6.1 | 7 / 39 | |
| 5.6.0 | 7 / 39 | |
| 5.5.0 | 7 / 39 | |
| 5.4.4 | 7 / 39 | |
| 5.4.3 | 7 / 39 | |
| 5.4.2 | 7 / 38 | |
| 5.4.1 | 7 / 38 | |
| 5.4.0 | 7 / 38 | |
| 5.3.0 | 7 / 38 | |
| 5.2.1 | 7 / 37 | |
| 5.2.0 | 7 / 37 | |
| 5.1.1 | 7 / 37 | |
| 5.1.0 | 7 / 37 | |
| 5.0.1 | 7 / 37 | |
| 5.0.0 | 7 / 37 | |
| 4.3.2 | 7 / 37 |
v5.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.