parse-author
Parse an author, contributor, maintainer or other 'person' string into an object with name, email and url properties following npm conventions.
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 | publisher-changed | AI (provenance): Legitimate maintainer transition from contributor slang800 to repo owner jonschlinkert, both listed in package.json contributors. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 328-day gap explained by maintainer transition; jonschlinkert is a trusted prolific publisher with 1863 approved packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): author-regex is jonschlinkert's own package, a natural regex extraction for this utility. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 1 | |
| 1.0.0 | 0 / 2 | |
| 0.2.2 | 1 / 2 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.0 | 1 / 4 |
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-03-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.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-14. This could indicate a legitimate maintainer transition or an account compromise.