user-meta
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
sapegin
Keywords
npmnpmrcgitgitconfignameusernameuserurlconfigconfiguration
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used legitimately to read git/npm config for user metadata — core functionality of this package, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package is ~8.6 years old, predating npm provenance attestation. Single-version package with no updates expected; absence of provenance is not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 4 |
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.