@open-rpc/meta-schema
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:build/index.js | AI (source-diff): build/index.js is the generated OpenRPC JSON schema as a JS object, one long line — not obfuscation. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Schema validator referenced in config; stable pattern for this package type. | ai | |
| phantom-deps | phantom-dep:djv | AI (phantom-deps): Schema validator referenced in config; stable pattern for this package type. | ai | |
| phantom-deps | phantom-dep:@open-rpc/examples | AI (phantom-deps): Same-org dependency referenced in config; stable for schema distribution package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal payload is expected for a schema-only package; not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@semantic-release/commit-analyzer | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:semantic-release | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:@semantic-release/release-notes-generator | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:@semantic-release/git | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:@semantic-release/npm | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:@semantic-release/github | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai | |
| phantom-deps | phantom-dep:@semantic-release/changelog | AI (phantom-deps): CI tooling referenced via config, not imported; benign misplacement. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.14.9 | 0 / 19 | |
| 1.13.7 | 0 / 8 | |
| 1.13.6 | 0 / 8 | |
| 1.13.5 | 0 / 8 | |
| 1.13.4 | 0 / 8 | |
| 1.13.0 | 10 / 10 | |
| 1.12.7 | 0 / 10 | |
| 1.12.5 | 7 / 11 | |
| 1.12.4 | 7 / 11 | |
| 1.12.3 | 7 / 11 | |
| 1.12.2 | 7 / 11 | |
| 1.12.1 | 7 / 11 | |
| 1.12.0 | 7 / 11 | |
| 1.11.1 | 7 / 9 | |
| 1.11.0 | 7 / 9 | |
| 1.10.2 | 7 / 9 | |
| 1.10.1 | 7 / 9 | |
| 1.10.0 | 7 / 9 | |
| 1.9.1 | 0 / 9 | |
| 1.9.0 | 0 / 9 | |
| 1.8.0 | 0 / 9 | |
| 1.7.3 | 0 / 10 | |
| 1.7.2 | 0 / 10 | |
| 1.7.1 | 0 / 10 | |
| 1.7.0 | 0 / 10 | |
| 1.6.0 | 0 / 10 | |
| 1.5.4 | 0 / 9 | |
| 1.5.3 | 0 / 9 | |
| 1.5.2 | 0 / 9 | |
| 1.5.1 | 0 / 9 | |
| 1.5.0 | 0 / 9 | |
| 1.4.3 | 0 / 9 | |
| 1.4.2 | 0 / 9 | |
| 1.4.1 | 0 / 9 | |
| 1.4.0 | 0 / 9 | |
| 1.3.2 | 0 / 8 | |
| 1.3.1 | 0 / 8 | |
| 1.3.0 | 0 / 7 | |
| 1.2.3 | 2 / 5 | |
| 1.2.2 | 2 / 5 | |
| 1.2.1 | 3 / 4 | |
| 1.2.0 | 3 / 4 | |
| 1.1.0 | 3 / 4 | |
| 1.0.6 | 3 / 4 | |
| 1.0.5 | 3 / 4 | |
| 1.0.4 | 3 / 4 | |
| 1.0.3 | 3 / 1 | |
| 1.0.2 | 3 / 1 | |
| 1.0.1 | 3 / 1 | |
| 1.0.0 | 3 / 1 |
v1.13.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.