@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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: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 | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @golemio org package; Levenshtein match to 'pino' is coincidental. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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 |
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.