prettier-plugin-hermes-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:index.mjs | AI (source-diff): Generated bundle with @generated header; deps inlined intentionally. Stable pattern for this package going forward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with major packaging refactor; trusted publisher with strong track record. | ai | |
| phantom-deps | phantom-dep:hermes-estree | AI (phantom-deps): hermes-estree is a legitimate transitive dep used by hermes-parser; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-hermes-parser | AI (phantom-deps): Self-referential config entry; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Meta/Facebook package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.36.1 | 0 / 0 | |
| 0.36.0 | 0 / 0 | |
| 0.35.0 | 0 / 0 | |
| 0.34.1 | 0 / 0 | |
| 0.34.0 | 0 / 0 | |
| 0.33.2 | 0 / 0 | |
| 0.33.1 | 0 / 0 | |
| 0.33.0 | 0 / 0 | |
| 0.32.0 | 0 / 0 | |
| 0.31.1 | 0 / 0 | |
| 0.31.0 | 3 / 0 | |
| 0.30.0 | 3 / 0 | |
| 0.29.1 | 3 / 0 | |
| 0.29.0 | 3 / 0 | |
| 0.28.1 | 3 / 0 | |
| 0.28.0 | 3 / 0 | |
| 0.27.0 | 3 / 0 | |
| 0.26.0 | 3 / 0 | |
| 0.25.1 | 3 / 0 | |
| 0.25.0 | 3 / 0 | |
| 0.24.0 | 3 / 0 | |
| 0.23.1 | 3 / 0 | |
| 0.23.0 | 3 / 0 | |
| 0.22.0 | 3 / 0 | |
| 0.21.1 | 3 / 0 | |
| 0.21.0 | 3 / 0 |
v0.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.