php-parser
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:dist/php-parser.js | AI (source-diff): dist is a webpack bundle with build banner, not obfuscation; expected build output. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Documented long-standing maintainer handoff to czosel; stable across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate transfer to listed contributor czosel. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.7.0 | 0 / 24 | |
| 3.6.0 | 0 / 24 | |
| 3.5.1 | 0 / 24 | |
| 3.5.0 | 0 / 24 | |
| 3.4.0 | 0 / 24 | |
| 3.3.0 | 0 / 24 | |
| 3.2.5 | 0 / 24 | |
| 3.2.4 | 0 / 24 | |
| 3.2.3 | 0 / 25 | |
| 3.2.2 | 0 / 25 | |
| 3.2.1 | 0 / 25 | |
| 3.2.0 | 0 / 19 | |
| 3.1.5 | 0 / 19 | |
| 3.1.4 | 0 / 19 | |
| 3.1.3 | 0 / 19 | |
| 3.1.2 | 0 / 19 | |
| 3.1.1 | 0 / 19 | |
| 3.1.0 | 0 / 19 | |
| 3.0.3 | 0 / 17 | |
| 3.0.2 | 0 / 16 | |
| 3.0.1 | 0 / 16 | |
| 3.0.0 | 0 / 16 |
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2023-06-07. It has since remained available on npm for 1140 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2023-03-21. It has since remained available on npm for 1218 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2023-01-11. It has since remained available on npm for 1287 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2022-11-01. It has since remained available on npm for 1358 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2022-09-13. It has since remained available on npm for 1407 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This version was published by a different npm account (czosel) than the most recent previously approved version (ichiriac) on 2022-08-10. It has since remained available on npm for 1441 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.