@custom-elements-manifest/analyzer
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
passle
Keywords
custom-elementscustom-elements-jsoncustom-elements-manifestcustomelementswebcomponentscustomelementsjsoncustomelementsmanifest
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Stable long-running package versioned 0.0.0 by design, not a throwaway. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Reads local project's own package.json for manifest metadata; benign CLI pattern. | ai | |
| source-diff | obfuscated-file:browser/index.js | AI (source-diff): Rollup-bundled browser build output, not true obfuscation; matches build:browser script. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is the new bundled browser/index.js build artifact, not injected payload. | ai | |
| provenance | no-provenance | AI (provenance): Established open-wc org package; lack of provenance is consistent across all 118 versions and is not a risk signal here. | ai |
Versions (showing 1 of 101)
| Version | Deps | Published |
|---|---|---|
| 0.0.0 | 2 / 14 |
v0.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.