publish-please
Safe and highly functional replacement for `npm publish`.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): micromatch is a well-established glob library; its addition as a replacement for globby/ban-sensitive-files is a routine maintenance change for a publish tool. | ai | |
| phantom-deps | phantom-dep:promisify-event | AI (phantom-deps): promisify-event is a declared dependency used indirectly; not a security concern for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): publish-please's preinstall script is part of its documented setup flow; it has been present across all versions of this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): publish-please's postinstall script initializes configuration in the consuming project; this is core documented functionality stable across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads init.js from the project directory — this is publish-please's documented initialization pattern, not arbitrary code loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): publish-please is a CLI publishing tool; child_process usage to run npm commands is expected and inherent to its purpose. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 5.5.2 | 10 / 14 | |
| 5.5.1 | 10 / 14 | |
| 5.5.0 | 10 / 14 | |
| 5.4.1 | 10 / 14 | |
| 5.3.0 | 10 / 14 | |
| 5.2.0 | 9 / 14 | |
| 5.1.1 | 9 / 14 | |
| 5.0.0 | 13 / 16 | |
| 4.1.0 | 14 / 16 | |
| 4.0.1 | 14 / 16 | |
| 3.2.0 | 14 / 16 | |
| 3.1.1 | 14 / 16 | |
| 3.1.0 | 14 / 16 | |
| 3.0.3 | 14 / 16 | |
| 3.0.2 | 14 / 16 | |
| 3.0.1 | 14 / 16 | |
| 3.0.0 | 14 / 16 | |
| 2.4.1 | 14 / 9 | |
| 2.4.0 | 14 / 9 | |
| 2.3.1 | 14 / 9 | |
| 2.3.0 | 14 / 9 | |
| 2.2.0 | 14 / 9 | |
| 2.1.4 | 13 / 9 | |
| 2.1.3 | 13 / 9 | |
| 2.1.2 | 14 / 9 | |
| 2.1.1 | 14 / 9 | |
| 2.1.0 | 14 / 9 | |
| 2.0.0 | 13 / 6 | |
| 1.4.3 | 14 / 4 | |
| 1.3.10 | 13 / 6 | |
| 1.3.9 | 13 / 6 | |
| 1.3.8 | 13 / 6 | |
| 1.3.3 | 13 / 6 | |
| 1.1.0 | 14 / 4 | |
| 1.0.1 | 12 / 2 |
v5.5.2
4 findingsScript: node lib/pre-install.js
Script: node lib/post-install.js
This version was published by a different npm account than previous versions on 2020-10-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.