← Home

@manypkg/tools

npm Repository Homepage
7
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

emmatowndcousens

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed from manypkg-release-bot to GitHub Actions as part of a CI/CD migration to OIDC keyless publishing; consistent with SLSA attestation present on this version. ai
maintainer-change maintainer-added AI (maintainer-change): dcousens is a known open-source developer; addition is consistent with legitimate project maintainer transition alongside CI/CD migration. ai
maintainer-change maintainer-removed AI (maintainer-change): manypkg-release-bot removed as part of CI/CD migration to GitHub Actions OIDC publishing; not indicative of takeover given SLSA provenance attestation. ai

Versions (showing 7 of 7)

Version Deps Published
2.1.1 3 / 2
2.1.0 3 / 2
2.0.0 3 / 2
1.1.2 3 / 3
1.1.1 4 / 2
1.1.0 4 / 2
1.0.0 4 / 2

v2.1.1

2 findings
HIGH Publisher changed: manypkg-release-bot → GitHub Actions (on 2026-03-31) provenance

This version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

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.