← Home

mamacro

npm
4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

xtuc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Package is a legitimate minimal utility from a well-established publisher (xtuc) with 5 approved inbound dep edges and 8+ years in the registry; sparse metadata is not a risk signal here. ai
npm-metadata no-description AI (npm-metadata): Absence of description is a cosmetic issue for this established, trusted package; not a security concern. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance on npm; lack of attestation is expected for packages of this age. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.7 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.