@redocly/openapi-docs
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher shifted to GitHub Actions CI, consistent with legitimate CI/CD publishing. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Redocly package; missing README/repo metadata is a packaging quirk, not spam. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has strong track record; consistent with legitimate Redocly team transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): web-vitals is a well-known, benign Google metrics library. | ai | |
| phantom-deps | phantom-dep:prismjs | AI (phantom-deps): Used via config/highlighting, not direct import; long-standing pattern. | ai | |
| source-diff | obfuscated-file:lib/services/code-samples/httpsnippet/helpers/device-auth-snippets.js | AI (source-diff): Minified but fully readable OAuth2 device-flow code generation; no malicious patterns present. | ai | |
| source-diff | encoded-string-file:dist/redocly-openapi-docs.min.js | AI (source-diff): Minified bundle; encoded strings are normal build output for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:jstoxml | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:swagger2openapi | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): False positive on minified JSX bundle; no actual raw IP URL present in the sample. | ai | |
| phantom-deps | phantom-dep:@redocly/openapi-core | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:stringify-object | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:util | AI (phantom-deps): Declared dep used in config/build context; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:slugify | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:web-vitals | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:json-pointer | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:url-template | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): Declared dep; phantom-dep heuristic misfires on bundled output. | ai |
Versions (showing 25 of 125)
| Version | Deps | Published |
|---|---|---|
| 3.2.12 | 23 / 45 | |
| 3.2.11 | 23 / 45 | |
| 3.2.10 | 23 / 45 | |
| 3.2.9 | 23 / 45 | |
| 3.2.8 | 23 / 45 | |
| 3.2.7 | 23 / 45 | |
| 3.2.6 | 23 / 45 | |
| 3.2.5 | 23 / 45 | |
| 3.2.4 | 23 / 45 | |
| 3.2.3 | 23 / 45 | |
| 3.2.2 | 23 / 45 | |
| 3.2.1 | 23 / 44 | |
| 3.2.0 | 23 / 44 | |
| 3.1.3 | 23 / 44 | |
| 3.1.2 | 23 / 48 | |
| 3.1.1 | 23 / 48 | |
| 3.1.0 | 23 / 48 | |
| 3.0.8 | 23 / 48 | |
| 3.0.7 | 23 / 48 | |
| 3.0.6 | 23 / 48 | |
| 3.0.5 | 23 / 48 | |
| 3.0.4 | 23 / 48 | |
| 3.0.3 | 23 / 48 | |
| 3.0.2 | 23 / 48 | |
| 3.0.1 | 23 / 48 |
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage 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.